netdev - Re: sfc: Replace LRO with GRO

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: <20090120115701.a273f3b9.sfr@canb.auug.org.au>
Date:	Tue, 20 Jan 2009 11:57:01 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Harvey Harrison <harvey.harrison@...il.com>
Cc:	David Miller <davem@...emloft.net>, bhutchings@...arflare.com,
	herbert@...dor.apana.org.au, netdev@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: sfc: Replace LRO with GRO

Hi,

On Mon, 19 Jan 2009 14:12:47 -0800 Harvey Harrison <harvey.harrison@...il.com> wrote:
>
> On Mon, 2009-01-19 at 13:29 -0800, David Miller wrote:
> > 
> > I haven't published my net-next-2.6 tree at all, because
> > Stephen Rothwell hasn't stated that such content is
> > OK yet for his -next tree.
> 
> I thought Stephen had stated that anytime _after_ -rc1 was released was
> OK for new material destined for the next release.
> 
> If you're waiting for an explicit OK, I don't think it will forthcoming.

Here it is: "OK".  :-)

Yeah any time after -rc1 is fine.  I thought -rc2 would be better, but
Andrew beat me into submission :-)  (I suspect he suffers more from that
decision then I do).

It also has the advantage of ruining LCA for you all. :-)
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped