From: Fernando Luis Vazquez Cao <fernando_b1@lab.ntt.co.jp>
To: David Miller <davem@davemloft.net>
Cc: bhutchings@solarflare.com, kaber@trash.net, netdev@vger.kernel.org
Subject: Re: [PATCH] vlan: restore ethtool ABI to control VLAN hardware acceleration
Date: Tue, 18 Jun 2013 10:38:14 +0900 [thread overview]
Message-ID: <51BFBA06.7050901@lab.ntt.co.jp> (raw)
In-Reply-To: <20130617.171001.1255646251913428917.davem@davemloft.net>
On 2013年06月18日 09:10, David Miller wrote:
> From: Ben Hutchings <bhutchings@solarflare.com>
> Date: Mon, 17 Jun 2013 19:20:54 +0100
>
>> On Mon, 2013-06-17 at 11:28 +0900, Fernando Luis Vázquez Cao wrote:
>>> As part of the push to add 802.1ad server provider tagging support to the
>>> kernel the VLAN features flags were renamed. Unfortunately the kernel name
>>> for the VLAN hardware acceleration features that the kernel shows user space
>>> was included in the rename, which broke ethtool (txvlan and rxvlan options
>>> do not work).
>> I expected something like that and said this was an ABI change, but
>> apparently my objection wasn't sufficient.
>>
>>> This patch restores the original names, i.e. the original ABI.
>>> If we wanted to make clear to users that we are refering to CTAGs we can
>>> always change ethtool's short_name and long_name for these features (for
>>> example something along the lines of txvlan -> txvlan-ctag, tx-vlan-offload ->
>>> tx-vlan-ctag-offload).
>>>
>>> Cc: Patrick McHardy <kaber@trash.net>
>>> Cc: David S. Miller <davem@davemloft.net>
>>> Cc: netdev@vger.kernel.org
>>> Signed-off-by: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>
>> Reviewed-by: Ben Hutchings <bhutchings@solarflare.com>
> Ok Ben you were indeed right :-)
>
> Applied, thanks.
Could you get this to Linus before 3.10 is out?
Thanks,
Fernando
next prev parent reply other threads:[~2013-06-18 1:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 2:28 [PATCH] vlan: restore ethtool ABI to control VLAN hardware acceleration Fernando Luis Vázquez Cao
2013-06-17 18:20 ` Ben Hutchings
2013-06-18 0:10 ` David Miller
2013-06-18 1:38 ` Fernando Luis Vazquez Cao [this message]
2013-06-18 7:18 ` David Miller
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=51BFBA06.7050901@lab.ntt.co.jp \
--to=fernando_b1@lab.ntt.co.jp \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.