From: David Ahern <dsahern@gmail.com>
To: John Hurley <john.hurley@netronome.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, jiri@mellanox.com, xiyou.wangcong@gmail.com,
willemdebruijn.kernel@gmail.com, stephen@networkplumber.org,
simon.horman@netronome.com, jakub.kicinski@netronome.com,
oss-drivers@netronome.com
Subject: Re: [PATCH iproute2-next v2 0/3] add interface to TC MPLS actions
Date: Wed, 10 Jul 2019 15:08:05 -0600 [thread overview]
Message-ID: <15257a97-f710-3192-6a28-8680ed89ee5a@gmail.com> (raw)
In-Reply-To: <1562762440-25656-1-git-send-email-john.hurley@netronome.com>
On 7/10/19 6:40 AM, John Hurley wrote:
> Recent kernel additions to TC allows the manipulation of MPLS headers as
> filter actions.
>
> The following patchset creates an iproute2 interface to the new actions
> and includes documentation on how to use it.
>
> v1->v2:
> - change error from print_string() to fprintf(strerr,) (Stephen Hemminger)
> - split long line in explain() message (David Ahern)
> - use _SL_ instead of /n in print message (David Ahern)
>
> John Hurley (3):
> lib: add mpls_uc and mpls_mc as link layer protocol names
> tc: add mpls actions
> man: update man pages for TC MPLS actions
>
> lib/ll_proto.c | 2 +
> man/man8/tc-mpls.8 | 156 ++++++++++++++++++++++++++++++
> tc/Makefile | 1 +
> tc/m_mpls.c | 276 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 435 insertions(+)
> create mode 100644 man/man8/tc-mpls.8
> create mode 100644 tc/m_mpls.c
>
applied to iproute2-next. Thanks
prev parent reply other threads:[~2019-07-10 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 12:40 [PATCH iproute2-next v2 0/3] add interface to TC MPLS actions John Hurley
2019-07-10 12:40 ` [PATCH iproute2-next v2 1/3] lib: add mpls_uc and mpls_mc as link layer protocol names John Hurley
2019-07-10 12:40 ` [PATCH iproute2-next v2 2/3] tc: add mpls actions John Hurley
2019-07-10 12:40 ` [PATCH iproute2-next v2 3/3] man: update man pages for TC MPLS actions John Hurley
2019-07-10 21:08 ` David Ahern [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=15257a97-f710-3192-6a28-8680ed89ee5a@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@mellanox.com \
--cc=john.hurley@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=simon.horman@netronome.com \
--cc=stephen@networkplumber.org \
--cc=willemdebruijn.kernel@gmail.com \
--cc=xiyou.wangcong@gmail.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).