From: David Miller <davem@davemloft.net>
To: makita.toshiaki@lab.ntt.co.jp
Cc: kaber@trash.net, ariel.elior@qlogic.com, amirv@mellanox.com,
shahed.shaikh@qlogic.com, Dept-GELinuxNICDev@qlogic.com,
j.vosburgh@gmail.com, vfalico@gmail.com,
gospo@cumulusnetworks.com, jiri@resnulli.us,
linux.nics@intel.com, vyasevic@redhat.com,
eric.dumazet@gmail.com, netdev@vger.kernel.org,
e1000-devel@lists.sourceforge.net
Subject: Re: [PATCH v2 net-next 0/7] Stacked vlan TSO
Date: Sun, 29 Mar 2015 13:33:52 -0700 (PDT) [thread overview]
Message-ID: <20150329.133352.867508831024428833.davem@davemloft.net> (raw)
In-Reply-To: <1427434277-27569-1-git-send-email-makita.toshiaki@lab.ntt.co.jp>
From: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
Date: Fri, 27 Mar 2015 14:31:09 +0900
> On the basis of Netdev 0.1 discussion[1], I made a patch set to enable
> TSO for packets with multiple vlans.
Series applied, thank you.
prev parent reply other threads:[~2015-03-29 20:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 5:31 [PATCH v2 net-next 0/7] Stacked vlan TSO Toshiaki Makita
2015-03-27 5:31 ` [PATCH v2 net-next 1/7] vlan: Add features for stacked vlan device Toshiaki Makita
2015-03-27 5:31 ` [PATCH v2 net-next 2/7] vlan: Introduce helper functions to check if skb is tagged Toshiaki Makita
2015-03-27 5:31 ` [PATCH v2 net-next 3/7] net: Move check for multiple vlans to drivers Toshiaki Makita
2015-03-27 5:31 ` [PATCH v2 net-next 4/7] net: Introduce passthru_features_check Toshiaki Makita
2015-03-27 5:31 ` [PATCH v2 net-next 5/7] bonding: Don't segment multiple tagged packets on bonding device Toshiaki Makita
2015-03-27 5:31 ` [PATCH v2 net-next 6/7] team: Don't segment multiple tagged packets on team device Toshiaki Makita
2015-03-27 5:31 ` [PATCH v2 net-next 7/7] igb: Enable TSO for stacked vlan Toshiaki Makita
2015-03-29 20:33 ` 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=20150329.133352.867508831024428833.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Dept-GELinuxNICDev@qlogic.com \
--cc=amirv@mellanox.com \
--cc=ariel.elior@qlogic.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=eric.dumazet@gmail.com \
--cc=gospo@cumulusnetworks.com \
--cc=j.vosburgh@gmail.com \
--cc=jiri@resnulli.us \
--cc=kaber@trash.net \
--cc=linux.nics@intel.com \
--cc=makita.toshiaki@lab.ntt.co.jp \
--cc=netdev@vger.kernel.org \
--cc=shahed.shaikh@qlogic.com \
--cc=vfalico@gmail.com \
--cc=vyasevic@redhat.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).