From: David Miller <davem@davemloft.net>
To: a.heider@gmail.com
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
stable@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [ 000/100] 3.8.3-stable review
Date: Wed, 13 Mar 2013 04:33:43 -0400 (EDT) [thread overview]
Message-ID: <20130313.043343.704615564539285477.davem@davemloft.net> (raw)
In-Reply-To: <CAHsu+b9O+JG=v6FgAEG4KOVDGScFiZYQm_nqXOQ9NSae3D3hwA@mail.gmail.com>
From: Andre Heider <a.heider@gmail.com>
Date: Wed, 13 Mar 2013 09:02:46 +0100
> On Tue, Mar 12, 2013 at 11:30 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
>> This is the start of the stable review cycle for the 3.8.3 release.
>> There are 100 patches in this series, all will be posted as a response
>> to this one. If anyone has any issues with these being applied, please
>> let me know.
>
> Hi,
>
> I'm missing a drivers/net/ethernet/atheros/atl1c patch, namely "atl1c:
> restore buffer state".
> In fact, it seems the whole netdev stable patch queue is missing:
> http://patchwork.ozlabs.org/bundle/davem/stable/?state=*
>
> Unsure what the workflow is here, how are these supposed to make to stable?
I submit those patches at a time of my own choosing, and if you
read stable@vger.kernel.org you will see when I do that.
I let patches cook in Linus's tree for a week or so before submitting
to -stable so that any bugs in those changes are more likely to be
discovered before the change is in -stable too.
next prev parent reply other threads:[~2013-03-13 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130312223122.884099393@linuxfoundation.org>
2013-03-13 8:02 ` [ 000/100] 3.8.3-stable review Andre Heider
2013-03-13 8:33 ` David Miller [this message]
2013-03-13 9:13 ` Andre Heider
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=20130313.043343.704615564539285477.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.heider@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox