From: David Miller <davem@davemloft.net>
To: aduyck@mirantis.com
Cc: jesse@kernel.org, netdev@vger.kernel.org,
alexander.duyck@gmail.com, tom@herbertland.com
Subject: Re: [net-next PATCH] netdev_features: Add NETIF_F_TSO_MANGLEID to NETIF_F_ALL_TSO
Date: Sat, 16 Apr 2016 19:15:07 -0400 (EDT) [thread overview]
Message-ID: <20160416.191507.383764314303192016.davem@davemloft.net> (raw)
In-Reply-To: <20160414210434.14117.52071.stgit@ahduyck-xeon-server>
From: Alexander Duyck <aduyck@mirantis.com>
Date: Thu, 14 Apr 2016 17:04:34 -0400
> I realized that when I added NETIF_F_TSO_MANGLEID as a TSO type I forgot to
> add it to NETIF_F_ALL_TSO. This patch corrects that so the flag will be
> included correctly.
>
> The result should be minor as it was only used by a few drivers and in a
> few specific cases such as when NETIF_F_SG was not supported on a device so
> the TSO flags were cleared.
>
> Signed-off-by: Alexander Duyck <aduyck@mirantis.com>
Applied.
prev parent reply other threads:[~2016-04-16 23:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 21:04 [net-next PATCH] netdev_features: Add NETIF_F_TSO_MANGLEID to NETIF_F_ALL_TSO Alexander Duyck
2016-04-16 23:15 ` 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=20160416.191507.383764314303192016.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aduyck@mirantis.com \
--cc=alexander.duyck@gmail.com \
--cc=jesse@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.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).