From: Stephen Hemminger <stephen@networkplumber.org>
To: Simon Horman <simon.horman@netronome.com>
Cc: netdev@vger.kernel.org, Jiri Pirko <jiri@mellanox.com>
Subject: Re: [PATCH v2 iproute2/net-next 0/3] tc: flower: Support matching on ICMP
Date: Wed, 7 Dec 2016 09:21:55 -0800 [thread overview]
Message-ID: <20161207092155.4d51ca84@xeon-e3> (raw)
In-Reply-To: <1481118843-10428-1-git-send-email-simon.horman@netronome.com>
On Wed, 7 Dec 2016 14:54:00 +0100
Simon Horman <simon.horman@netronome.com> wrote:
> Add support for matching on ICMP type and code to flower. This is modeled
> on existing support for matching on L4 ports.
>
> The second patch provided a minor cleanup which is in keeping with
> they style used in the last patch.
>
> This is marked as an RFC to match the same designation given to the
> corresponding kernel patches.
>
>
> Changes since v1:
> * Rebase
> * Do not run noths() on u8 entity
>
> Simon Horman (3):
> tc: flower: update headers for TCA_FLOWER_KEY_ICMP*
> tc: flower: introduce enum flower_endpoint
> tc: flower: support matching on ICMP type and code
>
> include/linux/pkt_cls.h | 10 ++++
> man/man8/tc-flower.8 | 20 ++++++--
> tc/f_flower.c | 123 +++++++++++++++++++++++++++++++++++++++++++-----
> 3 files changed, 135 insertions(+), 18 deletions(-)
>
I am holding of applying these to net-next until David applies kernel
portion.
prev parent reply other threads:[~2016-12-07 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 13:54 [PATCH v2 iproute2/net-next 0/3] tc: flower: Support matching on ICMP Simon Horman
2016-12-07 13:54 ` [PATCH v2 iproute2/net-next 1/3] tc: flower: update headers for TCA_FLOWER_KEY_ICMP* Simon Horman
2016-12-09 20:47 ` Stephen Hemminger
2016-12-07 13:54 ` [PATCH v2 iproute2/net-next 2/3] tc: flower: introduce enum flower_endpoint Simon Horman
2016-12-09 20:47 ` Stephen Hemminger
2016-12-07 13:54 ` [PATCH v2 iproute2/net-next 3/3] tc: flower: support matching on ICMP type and code Simon Horman
2016-12-09 20:48 ` Stephen Hemminger
2016-12-07 17:21 ` 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=20161207092155.4d51ca84@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@netronome.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).