From: Stephen Hemminger <stephen@networkplumber.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, idosch@mellanox.com,
yotamg@mellanox.com, mlxsw@mellanox.com, Yuval.Mintz@cavium.com
Subject: Re: [patch iproute2] tc: flower: add support for tcp flags
Date: Tue, 30 May 2017 17:43:09 -0700 [thread overview]
Message-ID: <20170530174309.1e78a104@xeon-e3> (raw)
In-Reply-To: <20170523215139.2019-1-jiri@resnulli.us>
On Tue, 23 May 2017 23:51:39 +0200
Jiri Pirko <jiri@resnulli.us> wrote:
> From: Jiri Pirko <jiri@mellanox.com>
>
> Allow user to insert a flower classifier filter rule which includes
> match for tcp flags.
>
> Signed-off-by: Jiri Pirko <jiri@mellanox.com>
Applied to net-next
next prev parent reply other threads:[~2017-05-31 0:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 16:40 [patch net-next v2 0/5] add tcp flags match support to flower and offload it Jiri Pirko
2017-05-23 16:40 ` [patch net-next v2 1/5] net: flow_dissector: add support for dissection of tcp flags Jiri Pirko
2017-05-23 16:40 ` [patch net-next v2 2/5] net/sched: flower: add support for matching on " Jiri Pirko
2017-05-23 16:40 ` [patch net-next v2 3/5] mlxsw: acl: Add tcp flags acl element Jiri Pirko
2017-05-23 16:40 ` [patch net-next v2 4/5] mlxsw: spectrum: Add acl block containing tcp flags for ipv4 Jiri Pirko
2017-05-23 16:40 ` [patch net-next v2 5/5] mlxsw: spectrum_flower: Add support for tcp flags Jiri Pirko
2017-05-23 21:51 ` [patch iproute2] tc: flower: add " Jiri Pirko
2017-05-31 0:43 ` Stephen Hemminger [this message]
2017-05-24 20:24 ` [patch net-next v2 0/5] add tcp flags match support to flower and offload it David Miller
-- strict thread matches above, loose matches on Subject: below --
2017-05-23 14:31 [patch net-next " Jiri Pirko
2017-05-23 14:33 ` [patch iproute2] tc: flower: add support for tcp flags Jiri Pirko
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=20170530174309.1e78a104@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=Yuval.Mintz@cavium.com \
--cc=davem@davemloft.net \
--cc=idosch@mellanox.com \
--cc=jiri@resnulli.us \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).