All of lore.kernel.org
 help / color / mirror / Atom feed
From: mzoran@crowfest.net (Michael Zoran)
To: linux-arm-kernel@lists.infradead.org
Subject: outreachy/moving a driver out of staging
Date: Sun, 19 Mar 2017 00:37:47 -0700	[thread overview]
Message-ID: <1489909067.1536.14.camel@crowfest.net> (raw)
In-Reply-To: <20170309212021.GA24433@kroah.com>

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?

WARNING: multiple messages have this Message-ID (diff)
From: Michael Zoran <mzoran@crowfest.net>
To: Greg KH <gregkh@linuxfoundation.org>,
	Stephen Warren <swarren@wwwdotorg.org>
Cc: devel@driverdev.osuosl.org, f.fainelli@gmail.com,
	sbranden@broadcom.com, Julia Lawall <julia.lawall@lip6.fr>,
	rjui@broadcom.com, lee@kernel.org, linux-kernel@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com,
	linux-rpi-kernel@lists.infradead.org,
	Scott Branden <scott.branden@broadcom.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: outreachy/moving a driver out of staging
Date: Sun, 19 Mar 2017 00:37:47 -0700	[thread overview]
Message-ID: <1489909067.1536.14.camel@crowfest.net> (raw)
In-Reply-To: <20170309212021.GA24433@kroah.com>

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?

  parent reply	other threads:[~2017-03-19  7:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09 20:36 outreachy Julia Lawall
2017-03-09 20:36 ` outreachy Julia Lawall
2017-03-09 20:51 ` outreachy Scott Branden
2017-03-09 20:51   ` outreachy Scott Branden
2017-03-09 20:56   ` outreachy Stephen Warren
2017-03-09 20:56     ` outreachy Stephen Warren
2017-03-09 21:20     ` outreachy Greg KH
2017-03-09 21:20       ` outreachy Greg KH
2017-03-09 22:15       ` outreachy Florian Fainelli
2017-03-09 22:15         ` outreachy Florian Fainelli
2017-03-10  6:01         ` outreachy Greg KH
2017-03-10  6:01           ` outreachy Greg KH
2017-03-17 15:25       ` outreachy Pavel Machek
2017-03-17 15:25         ` outreachy Pavel Machek
2017-03-17 16:55         ` outreachy Julia Lawall
2017-03-17 16:55           ` outreachy Julia Lawall
2017-03-20 10:20           ` outreachy Pavel Machek
2017-03-20 10:20             ` outreachy Pavel Machek
2017-03-20 10:30             ` outreachy Greg KH
2017-03-20 10:30               ` outreachy Greg KH
2017-03-20 16:14               ` outreachy Pavel Machek
2017-03-20 16:14                 ` outreachy Pavel Machek
2017-03-19  7:37       ` Michael Zoran [this message]
2017-03-19  7:37         ` outreachy/moving a driver out of staging Michael Zoran
2017-03-19  9:15         ` Russell King - ARM Linux
2017-03-19  9:15           ` Russell King - ARM Linux
2017-03-19 10:22           ` Michael Zoran
2017-03-19 10:22             ` Michael Zoran

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1489909067.1536.14.camel@crowfest.net \
    --to=mzoran@crowfest.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.