From: Alexander Duyck <alexander.h.duyck@redhat.com>
To: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] ixgbe: Remove NETIF_F_HW_VLAN_CTAG_FILTER from hw_features
Date: Thu, 12 Mar 2015 08:16:57 -0700 [thread overview]
Message-ID: <5501ADE9.8080507@redhat.com> (raw)
In-Reply-To: <7F861DC0615E0C47A872E6F3C5FCDDBD05E576A1@BPXM14GP.gisp.nec.co.jp>
On 03/11/2015 11:00 PM, Hiroshi Shimamoto wrote:
>> Subject: [PATCH] ixgbe: Remove NETIF_F_HW_VLAN_CTAG_FILTER from hw_features
>>
>> This change makes it so that the HW_VLAN_STAG_FILTER bit is not falsely
> s/STAG/CTAG/ right?
>
> thanks,
> Hiroshi
>
Yeah, I I'm not sure where the S came from. Maybe I was looking at
something else when I was typing.
I'll submit a v2 with updated patch comments.
- Alex
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
prev parent reply other threads:[~2015-03-12 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 3:03 [PATCH] ixgbe: Remove NETIF_F_HW_VLAN_CTAG_FILTER from hw_features Alexander Duyck
2015-03-12 6:00 ` Hiroshi Shimamoto
2015-03-12 15:16 ` Alexander Duyck [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=5501ADE9.8080507@redhat.com \
--to=alexander.h.duyck@redhat.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=h-shimamoto@ct.jp.nec.com \
--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).