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: <20090119.152717.147996116.davem@davemloft.net>
Date:	Mon, 19 Jan 2009 15:27:17 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	harvey.harrison@...il.com
Cc:	bhutchings@...arflare.com, herbert@...dor.apana.org.au,
	netdev@...r.kernel.org, sfr@...b.auug.org.au
Subject: Re: sfc: Replace LRO with GRO

From: Harvey Harrison <harvey.harrison@...il.com>
Date: Mon, 19 Jan 2009 14:12:47 -0800

> On Mon, 2009-01-19 at 13:29 -0800, David Miller wrote:
> > From: Ben Hutchings <bhutchings@...arflare.com>
> > > 
> > > Please could you push this and other GRO changes for .30 to
> > > net-next-2.6?
> > 
> > All of Herbert's bug fixes are going into net-2.6, and that's
> > where they will stay.
> > 
> > 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.

I, unlike some others, value Stephen Rothwell's sanity.  So I will ask
explicitly before potentially spoiling his afternoon :-)
--
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