From owner-freebsd-current@freebsd.org Mon May 20 11:21:47 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DCFC015AA0A2 for ; Mon, 20 May 2019 11:21:47 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5AF7D710F2 for ; Mon, 20 May 2019 11:21:47 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject; s=201508; t=1558351304; bh=Ps72xItT 1LfX0NAYbPix0N6YKE4KtxLWSzXqaevkgjg=; b=V85nUVO7o1hxga/LMAbaf3T7 MbkjbmJ6gTJ99D0ugNeQpWrMGLo1S66/jJuTD/0LhGZoH9lxKIjrqAM9HC8tUtdm csP6WGSZ7BBhaFBKlcbsKvyrGAeKe3TunzR+ZsvcPGizmGkE7izYv2pqThVL7S2K WlCsVeBrcHcez04qBCw= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 274B97F70 for ; Mon, 20 May 2019 07:21:44 -0400 (EDT) Subject: Re: Heads up for breaking drm update. To: freebsd-current@freebsd.org References: <20190520023605.GA64310@troutmask.apl.washington.edu> <94b816df-5cef-7578-5b68-e9c49d847f88@FreeBSD.org> From: Michael Butler Openpgp: preference=signencrypt Message-ID: Date: Mon, 20 May 2019 11:21:44 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: <94b816df-5cef-7578-5b68-e9c49d847f88@FreeBSD.org> Content-Type: text/plain; charset=windows-1252 Content-Language: en-NZ Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 May 2019 11:21:48 -0000 On 2019-05-19 23:21, Johannes Lundberg wrote: > > On 5/19/19 7:36 PM, Steve Kargl wrote: >> On Sun, May 19, 2019 at 02:50:54PM -0700, Johannes Lundberg wrote: >>> LinuxKPI in base have received a lot of updates recently for Linux 5.0, >>> a couple of them will break drm-current-kmod. So, as of r347973 you will >>> need drm-current-kmod 4.16.g20190519. Ports have been updated and new >>> packages should be available shortly. >>> >> If drm-current-kmod is broken, should I venture to ask >> about drm-stable-kmod and drm-legacy-kmod? > > That's a very good question. Maybe I should have included more > information regarding what's not affected. The last series of commits > have been to LinuxKPI in -CURRENT. As such: > > drm-kmod: Meta port, not relevant > drm-current-kmod: See original message > drm-fbsd11.2-kmod: Not affected by changes in -CURRENT > drm-fbsd12.0-kmod: Not affected by changes in -CURRENT > drm-legacy-kmod: Not affected by changes in LinuxKPI > > drm-stable-kmod does not exist anymore. Stable drm kmod ports for other > than -CURRENT are more or less frozen in separate branches where they > only receive bug fixes (drm-fbsdxxx-kmod). > > Hope that answers your questions. It should also be noted that drm-current now has a new dependency on lindebugfs. It won't load without it :-( imb