From: Stephen Hemminger <stephen@networkplumber.org>
To: Alexander Aring <aring@mojatatu.com>
Cc: jhs@mojatatu.com, yotamg@mellanox.com, xiyou.wangcong@gmail.com,
jiri@resnulli.us, lucasb@mojatatu.com, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] tc: act_ife: handle IEEE IFE ethertype as default
Date: Wed, 30 Aug 2017 08:27:32 -0700 [thread overview]
Message-ID: <20170830082732.365864e3@xeon-e3> (raw)
In-Reply-To: <20170828190315.26646-1-aring@mojatatu.com>
On Mon, 28 Aug 2017 15:03:12 -0400
Alexander Aring <aring@mojatatu.com> wrote:
> Hi,
>
> this patch series will introduce the IFE ethertype which is registered by
> IEEE. If the netlink act_ife type netlink attribute is not given it will
> use this value by default now.
> At least it will introduce some UAPI testcases to check if the default type
> is used if not specified and vice versa.
>
> - Alex
>
> Alexander Aring (3):
> if_ether: add forces ife lfb type
> act_ife: use registered ife_type as fallback
> tc-testing: add test for testing ife type
>
> include/uapi/linux/if_ether.h | 1 +
> net/sched/act_ife.c | 17 ++------
> .../tc-testing/tc-tests/actions/tests.json | 50 ++++++++++++++++++++++
> 3 files changed, 54 insertions(+), 14 deletions(-)
>
Applied to net-next
prev parent reply other threads:[~2017-08-30 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 19:03 [PATCH net-next 0/3] tc: act_ife: handle IEEE IFE ethertype as default Alexander Aring
2017-08-28 19:03 ` [PATCH net-next 1/3] if_ether: add forces ife lfb type Alexander Aring
2017-08-28 22:03 ` Jamal Hadi Salim
2017-08-28 19:03 ` [PATCH net-next 2/3] act_ife: use registered ife_type as fallback Alexander Aring
2017-08-28 22:14 ` Jamal Hadi Salim
2017-08-28 19:03 ` [PATCH net-next 3/3] tc-testing: add test for testing ife type Alexander Aring
2017-08-28 22:16 ` Jamal Hadi Salim
2017-08-29 22:14 ` [PATCH net-next 0/3] tc: act_ife: handle IEEE IFE ethertype as default David Miller
2017-08-30 15:27 ` Stephen Hemminger [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=20170830082732.365864e3@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=aring@mojatatu.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=linux-kselftest@vger.kernel.org \
--cc=lucasb@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
--cc=yotamg@mellanox.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