From: David Miller <davem@davemloft.net>
To: sri@us.ibm.com
Cc: herbert@gondor.apana.org.au, rusty@rustcorp.com.au,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next-2.6] virtio_net: Set vlan_features to enable offloads on vlan devices
Date: Tue, 02 Feb 2010 07:46:52 -0800 (PST) [thread overview]
Message-ID: <20100202.074652.112999481.davem@davemloft.net> (raw)
In-Reply-To: <1264454176.28852.129.camel@w-sridhar.beaverton.ibm.com>
From: Sridhar Samudrala <sri@us.ibm.com>
Date: Mon, 25 Jan 2010 13:16:16 -0800
> Set vlan_features in virtnet_probe() so that all the available offloads
> are enabled on vlan devices attached to virtio_net devices.
>
> Signed-off-by: Sridhar Samudrala <sri@us.ibm.com>
I can't apply this because I'm not going to apply your
patch which erroneously pops the VLAN header during GRO
processing. And this patch is useless without that.
prev parent reply other threads:[~2010-02-02 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 21:16 [PATCH net-next-2.6] virtio_net: Set vlan_features to enable offloads on vlan devices Sridhar Samudrala
2010-02-02 15:46 ` David Miller [this message]
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=20100202.074652.112999481.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sri@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).