From owner-freebsd-stable@freebsd.org Sun Aug 26 08:32:04 2018 Return-Path: Delivered-To: freebsd-stable@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 653EB106D847; Sun, 26 Aug 2018 08:32:04 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F144E76525; Sun, 26 Aug 2018 08:32:03 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 775862600C9; Sun, 26 Aug 2018 10:32:00 +0200 (CEST) Subject: Re: drm / drm2 removal in 12 To: blubee blubeeme , pmcnary@cameron.net Cc: Johannes Lundberg , freebsd-stable@freebsd.org, mmacy@freebsd.org, Ali Abdallah , FreeBSD current , =?UTF-8?Q?Dag-Erling_Sm=c3=b8rgrav?= References: <20180824215302.ivfna55jtrtc5trg@freebsd480.station> <86k1oepbdr.fsf@next.des.no> <180f8f99-5fa1-1411-59e6-856e3ebc370c@cameron.net> From: Hans Petter Selasky Message-ID: Date: Sun, 26 Aug 2018 10:31:36 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Aug 2018 08:32:04 -0000 On 8/26/18 3:20 AM, blubee blubeeme wrote: > Have you or anyone working on this drm-legacy-kmod stuff done any testings > of how this will affect current users? Hi Blubee, Are you here to try to stir a conflict? If so that is not appreciated. --HPS