netdev - Re: [ 000/100] 3.8.3-stable review

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20130313.043343.704615564539285477.davem@davemloft.net>
Date:	Wed, 13 Mar 2013 04:33:43 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	a.heider@...il.com
Cc:	gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	stable@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [ 000/100] 3.8.3-stable review

From: Andre Heider <a.heider@...il.com>
Date: Wed, 13 Mar 2013 09:02:46 +0100

> On Tue, Mar 12, 2013 at 11:30 PM, Greg Kroah-Hartman
> <gregkh@...uxfoundation.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@...r.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.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html