Re: outreachy/moving a driver out of staging

From	Michael Zoran <mzoran@crowfest.net>
Newsgroups	linux.kernel
Subject	Re: outreachy/moving a driver out of staging
Date	2017-03-19 08:40 +0100
Message-ID	<tmDBv-2m7-1@gated-at.bofh.it> (permalink)
References	<tjd0R-1Nu-3@gated-at.bofh.it> <tjdkd-1Wq-1@gated-at.bofh.it> <tjdke-1Wq-3@gated-at.bofh.it> <tjdWV-2rg-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Thu, 2017-03-09 at 22:20 +0100, Greg KH wrote:
> On Thu, Mar 09, 2017 at 01:56:49PM -0700, Stephen Warren wrote:
> > On 03/09/2017 01:51 PM, Scott Branden wrote:
> > > Hi Julia,
> > > 
> > > On 17-03-09 12:36 PM, Julia Lawall wrote:
> > > > Hello,
> > > > 
> > > > I discussed the issue of outreachy patches for bcm with Greg,
> > > > and we are
> > > > not convinced that not having the patches CCd to you is such a
> > > > good idea.
> > > > While we don't want to spam you with noise, some of the
> > > > applicants are
> > > > starting to make more significant changes that it could be
> > > > useful for you
> > > > to be aware of.
> > > > 
> > > > Could we try a compromise where you are not CCd on whitespace
> > > > patches,
> > > > but
> > > > you are CCd on patches that actually modify the code?
> > > 
> > > All I'm asking is you work through your outreachy patches
> > > internal first
> > > to get rid of the most basic mistakes and email traffic it is
> > > geerating.
> > >  Once that learning process is through then they can be sent out
> > > like
> > > any other patches to the kernel mailing lists and maintainers.
> > 
> > +1 from me too; I find these patches rather high volume and had to
> > add a
> > filter to keep them out of my primary inbox.
> 
> Hah!  That's the joy of being a maintainer of a driver in
> staging.  Even
> if you filter out outreachy, you are going to get a lot of "basic
> mistakes" and other type patches cc:ed to you.
> 
> I strongly suggest, that if you all don't like this type of stuff,
> either:
> 	- work to get the code out of staging as soon as possible (i.e.
> 	  send me coding style fixes for everything right now, and then
> 	  fix up the rest of the stuff.)
> 	- take yourself off the maintainer list for this code.
> 
> It's your choice, outreachy right now is a lot of patches, but again,
> it's not going to keep you from getting the "basic" stuff sent to you
> in ways that is totally wrong.
> 
> thanks,
> 
> greg k-h
> 

Hi Greg,

I just noticed this e-mail.  What exactly is the requirement to get a
driver or subsystem out of staging?

I can image a day when vc04_services or VideoCore gets moved out of
staging at some point. What exactly would it take to make something
like that happen?

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: outreachy/moving a driver out of staging Michael Zoran <mzoran@crowfest.net> - 2017-03-19 08:40 +0100
  Re: outreachy/moving a driver out of staging Russell King - ARM Linux <linux@armlinux.org.uk> - 2017-03-19 10:20 +0100
    Re: outreachy/moving a driver out of staging Michael Zoran <mzoran@crowfest.net> - 2017-03-19 12:00 +0100

csiph-web