From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Vetter Subject: Re: [PATCH V7 3/4] drm/bridge: Add driver for GE B850v3 LVDS/DP++ Bridge Date: Mon, 6 Feb 2017 09:45:45 +0100 Message-ID: <20170206084545.ke7riv6nacypqw2f@phenom.ffwll.local> References: <3e31-58931d80-1-221fa900@101383713> <20170203080040.qn53xnpojxzk4qoi@phenom.ffwll.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Emil Velikov Cc: Peter Senna Tschudin , Mark Rutland , martyn.welch-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org, Peter Senna Tschudin , ML dri-devel , "Linux-Kernel@Vger. Kernel. Org" , Yakir Yang , Jiri Slaby , Mauro Carvalho Chehab , Russell King - ARM Linux , Peter Senna Tschudin , javier-0uQlZySMnqxg9hUCZPvPmw@public.gmane.org, Thierry Reding , Guenter Roeck , martin.donnelly-JJi787mZWgc@public.gmane.org, devicetree , Pawel Moll , Ian Campbell , Fabio Estevam Ru List-Id: devicetree@vger.kernel.org On Fri, Feb 03, 2017 at 12:25:24PM +0000, Emil Velikov wrote: > On 3 February 2017 at 08:00, Daniel Vetter wrote: > > On Thu, Feb 02, 2017 at 12:37:21PM +0000, Emil Velikov wrote: > >> - Daniel, gents - is drm-misc aimed at devs with limited (no?) > >> review/commit history in the area and/or the kernel in general ? > >> In this case, Peter have quite noticeable experience [in kernel > >> development] with little-to no in DRM. > >> Should one draw a line in the sand somewhere ? > > > > We're fairly lenient with accepting new drivers already, and for drivers > > in drm-misc we require some checks and peer review to make sure new folks > > learn faster. But it's an expirement, I fully expect some fallout and then > > some learnign and fine tuning from that, and maybe we even need to crank > > requirements back up to a much higher level of experience. > > > > But for drivers I'm honestly not too concerned: As long as there's some > > process in place to foster learning&collaboration (which I think will be > > better with this) I really don't see much harm in merging non-perfect > > driver code. > > > Thank you Daniel, this is very well said. Being lenient to begin with > and adjusting where/if needed is the more welcoming approach, indeed. > Doubt there'll be (m)any cases of (ab|mis)use but even if so, nobody > can see the future. Yeah, the big idea behind drm-misc is also to make drm more welcoming for new folks, and I think starting with a small driver or a few driver patches for hw you have lying around for hacking is a great way. And every once in a while we can "trick" one of these newbies into doing some cool core refactoring or cleanup, and maybe even to stick around for a while. All for world domination and other evil purposes ofc :-) -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html