From: Florian Westphal <fw@strlen.de>
To: netdev@vger.kernel.org
Subject: [PATCH stable 3.4.y 0/2] gso/gro forwarding changeset
Date: Sat, 22 Feb 2014 10:33:24 +0100 [thread overview]
Message-ID: <1393061606-5422-1-git-send-email-fw@strlen.de> (raw)
Dropped the 2nd patch of the series (addition of netif_skb_dev_features)
for the longterm-backport.
The forward path will use 0 feature mask instead.
I think it is preferable to keep the changeset smaller for these kernels.
Should apply to 3.2.y as well.
Let me know if you disagree and would like to have netif_skb_dev_features
backport too.
next reply other threads:[~2014-02-22 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-22 9:33 Florian Westphal [this message]
2014-02-22 9:33 ` [PATCH 1/2] net: add and use skb_gso_transport_seglen() Florian Westphal
2014-02-22 9:33 ` [PATCH 2/2] net: ip, ipv6: handle gso skbs in forwarding path Florian Westphal
2014-04-06 13:16 ` [PATCH stable 3.4.y 0/2] gso/gro forwarding changeset Ben Hutchings
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=1393061606-5422-1-git-send-email-fw@strlen.de \
--to=fw@strlen.de \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).