Date: Fri, 28 Sep 2018 13:46:56 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Matthew Macy <mat.macy@gmail.com> Cc: Warner Losh <imp@bsdimp.com>, fullermd@over-yonder.net, freebsd-current <freebsd-current@freebsd.org> Subject: Re: drm2 in base Message-ID: <20180928204656.GD2631@troutmask.apl.washington.edu> In-Reply-To: <CAPrugNrf1BwDXXwxrdh-eeqNa=yr1f1ERApmcaPfV4h2KeS4oQ@mail.gmail.com> References: <20180928180002.GA957@troutmask.apl.washington.edu> <20180928194739.GH32731@over-yonder.net> <20180928200102.GA2631@troutmask.apl.washington.edu> <CANCZdfq0E=euENS_ougvDXB_p5pji6vwOhf0nMCuN_jEQmg6hQ@mail.gmail.com> <CAPrugNrf1BwDXXwxrdh-eeqNa=yr1f1ERApmcaPfV4h2KeS4oQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 28, 2018 at 01:30:59PM -0700, Matthew Macy wrote: > > Bug reports are addressed as they come in. If issues haven't come up > it likely reflects a scarcity of users. > It is likely that -current users are still using drm2 from base (or have sufficiently new hardware that drm-stable-kmod works for them). I saw Glen's post about the updated release schedule, and decided to be pro-active in moving to drm-*-kmod to counter the possibility that someone might remove drm2 from head as soon as the FreeBSD-12 branch exists. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180928204656.GD2631>