From owner-freebsd-current@freebsd.org Mon May 20 03:21:21 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 30EC0159F37F; Mon, 20 May 2019 03:21:21 +0000 (UTC) (envelope-from johalun@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 93CB0894EE; Mon, 20 May 2019 03:21:20 +0000 (UTC) (envelope-from johalun@FreeBSD.org) Received: from [IPv6:2600:8800:6900:b09:1265:30ff:fe82:52ff] (unknown [IPv6:2600:8800:6900:b09:1265:30ff:fe82:52ff]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: johalun) by smtp.freebsd.org (Postfix) with ESMTPSA id 2D0B317103; Mon, 20 May 2019 03:21:20 +0000 (UTC) (envelope-from johalun@FreeBSD.org) Subject: Re: Heads up for breaking drm update. To: sgk@troutmask.apl.washington.edu Cc: "freebsd-x11@freebsd.org" , FreeBSD Current References: <20190520023605.GA64310@troutmask.apl.washington.edu> From: Johannes Lundberg X-Tagtoolbar-Keys: D20190519202117920 Message-ID: <94b816df-5cef-7578-5b68-e9c49d847f88@FreeBSD.org> Date: Sun, 19 May 2019 20:21:18 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190520023605.GA64310@troutmask.apl.washington.edu> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: 93CB0894EE X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.97 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; NEURAL_HAM_SHORT(-0.97)[-0.968,0]; ASN(0.00)[asn:11403, ipnet:96.47.64.0/20, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] 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 03:21:21 -0000 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. /Johannes >