From: Greg KH <gregkh@linuxfoundation.org>
To: Joe Perches <joe@perches.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
devel@driverdev.osuosl.org,
Sudip Mukherjee <sudip@vectorindia.org>,
linux-wireless@vger.kernel.org, Stable <stable@vger.kernel.org>,
netdev@vger.kernel.org, Haggai Eran <haggai.eran@gmail.com>,
Arek Rusniak <arek.rusi@gmail.com>,
Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH] staging: r8712u: Fix kernel warning for improper call of del_timer_sync()
Date: Tue, 26 May 2015 13:30:47 -0700 [thread overview]
Message-ID: <20150526203047.GA21732@kroah.com> (raw)
In-Reply-To: <1432659977.2846.100.camel@perches.com>
On Tue, May 26, 2015 at 10:06:17AM -0700, Joe Perches wrote:
> On Tue, 2015-05-26 at 09:35 -0700, Greg KH wrote:
> > On Tue, May 26, 2015 at 07:48:59AM -0700, Joe Perches wrote:
> > > > > The main point is that patches shouldn't be applied without
> > > > > being submitted to a more widely read list.
> > > >
> > > > I take the blame for any problems with Outreachy patches.
> > >
> > > Are you going to change any procedure associated to these
> > > Outreachy patches?
> >
> > 2 bugs out of 900? Nah, I think that's good odds.
> >
> > Also, the outreachy patch process would overwhelm everyone else on the
> > list, it's really high volume during the application phase, I'd prefer
> > it to stick with the mentors that wish to help out with the process. If
> > you and/or Dan, or anyone else wishes to help out with this, I would
> > really appreciate it. But I don't think that forcing them to post to
> > the driverdevel list is a good idea.
>
> I don't think that's necessary, but sending them to any
> listed maintainer should be.
>
> If you're collecting them, I suggest you stick them in
> a separate branch, post them to your driverdev list and
> cc the appropriate maintainers, wait a week, then apply
> them to your main branch.
>
> You already batch post hundreds of patches for kernel
> x.y.z stable branches. What's another few hundred?
>
Stable patches is a totally different workflow from my "normal" kernel
patch acceptance work. I'll consider changing something for the future
outreachy application process.
thanks,
greg k-h
next prev parent reply other threads:[~2015-05-26 20:30 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 21:16 [PATCH] staging: r8712u: Fix kernel warning for improper call of del_timer_sync() Larry Finger
2015-05-24 19:03 ` Haggai Eran
2015-05-25 0:11 ` Larry Finger
2015-05-25 9:17 ` Dan Carpenter
2015-05-25 9:17 ` Dan Carpenter
[not found] ` <CAK-LDb+1WscLTFw=NDY=_aUOGw72a4wRsqCU-1N+KJ11k15S5w@mail.gmail.com>
2015-05-25 10:12 ` Dan Carpenter
2015-05-25 10:12 ` Dan Carpenter
2015-05-25 15:52 ` Larry Finger
2015-05-25 15:52 ` Larry Finger
2015-05-25 17:37 ` Joe Perches
2015-05-25 17:37 ` Joe Perches
2015-05-26 4:46 ` Sudip Mukherjee
2015-05-26 4:46 ` Sudip Mukherjee
2015-05-26 4:55 ` Joe Perches
2015-05-26 4:55 ` Joe Perches
2015-05-26 5:02 ` Sudip Mukherjee
2015-05-26 5:02 ` Sudip Mukherjee
2015-05-26 5:07 ` Joe Perches
2015-05-26 5:30 ` Sudip Mukherjee
2015-05-26 5:30 ` Sudip Mukherjee
2015-05-26 15:31 ` Larry Finger
2015-05-26 14:14 ` Greg KH
2015-05-26 14:14 ` Greg KH
2015-05-26 14:48 ` Joe Perches
2015-05-26 16:35 ` Greg KH
2015-05-26 17:06 ` Joe Perches
2015-05-26 20:25 ` Dan Carpenter
2015-05-26 20:25 ` Dan Carpenter
2015-05-26 20:30 ` Greg KH [this message]
2015-05-26 20:09 ` Dan Carpenter
2015-05-26 20:09 ` Dan Carpenter
2015-05-26 15:48 ` Dan Carpenter
2015-05-26 15:48 ` Dan Carpenter
2015-05-26 16:40 ` Larry Finger
2015-05-25 16:02 ` Larry Finger
2015-05-31 2:53 ` Greg KH
2015-05-31 2:53 ` Greg KH
2015-05-31 2:54 ` Greg KH
2015-05-31 2:54 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2015-05-25 4:42 Sudip Mukherjee
2015-05-25 15:59 ` Larry Finger
2015-05-25 15:59 ` Larry Finger
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=20150526203047.GA21732@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=arek.rusi@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=haggai.eran@gmail.com \
--cc=joe@perches.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=sudip@vectorindia.org \
--cc=sudipm.mukherjee@gmail.com \
/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.