From: Simon Horman <simon.horman@netronome.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, Simon Horman <simon.horman@netronome.com>
Subject: [PATCH iproute2 net-next 0/4] tc: flower: SCTP and other port fixes
Date: Tue, 29 Nov 2016 16:51:29 +0100 [thread overview]
Message-ID: <1480434693-29397-1-git-send-email-simon.horman@netronome.com> (raw)
Hi,
this short series:
* Makes some improvements to the documentation of flower;
A follow-up to recent work by Paul Blakey and myself.
* Corrects some errors introduced when SCTP port matching support was
recently added.
It applies on top of the following:
* [PATCH iproute2] tc: flower: Fix usage message
* [PATCH iproute2 0/2] tc: flower: Support matching on SCTP port
Simon Horman (4):
tc: flower: remove references to eth_type in manpage
tc: flower: document SCTP ip_proto
tc: flower: correct name of ip_proto parameter to flower_parse_port()
tc: flower: make use of flower_port_attr_type() safe and silent
man/man8/tc-flower.8 | 37 ++++++++++++++++++-------------------
tc/f_flower.c | 32 +++++++++++++++++---------------
2 files changed, 35 insertions(+), 34 deletions(-)
--
2.7.0.rc3.207.g0ac5344
next reply other threads:[~2016-11-29 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 15:51 Simon Horman [this message]
2016-11-29 15:51 ` [PATCH iproute2 net-next 1/4] tc: flower: remove references to eth_type in manpage Simon Horman
2016-11-29 15:51 ` [PATCH iproute2 net-next 2/4] tc: flower: document SCTP ip_proto Simon Horman
2016-12-01 18:50 ` Stephen Hemminger
2016-12-02 8:36 ` Simon Horman
2016-11-29 15:51 ` [PATCH iproute2 net-next 3/4] tc: flower: correct name of ip_proto parameter to flower_parse_port() Simon Horman
2016-11-29 15:51 ` [PATCH iproute2 net-next 4/4] tc: flower: make use of flower_port_attr_type() safe and silent Simon Horman
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=1480434693-29397-1-git-send-email-simon.horman@netronome.com \
--to=simon.horman@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).