From: David Miller <davem@davemloft.net>
To: john.hurley@netronome.com
Cc: netdev@vger.kernel.org, jiri@mellanox.com,
xiyou.wangcong@gmail.com, dsahern@gmail.com,
willemdebruijn.kernel@gmail.com, dcaratti@redhat.com,
mrv@mojatatu.com, simon.horman@netronome.com,
jakub.kicinski@netronome.com, oss-drivers@netronome.com
Subject: Re: [PATCH net-next v7 0/5] Add MPLS actions to TC
Date: Mon, 08 Jul 2019 20:05:09 -0700 (PDT) [thread overview]
Message-ID: <20190708.200509.2125973923907133864.davem@davemloft.net> (raw)
In-Reply-To: <1562508118-28841-1-git-send-email-john.hurley@netronome.com>
From: John Hurley <john.hurley@netronome.com>
Date: Sun, 7 Jul 2019 15:01:53 +0100
> This patchset introduces a new TC action module that allows the
> manipulation of the MPLS headers of packets. The code impliments
> functionality including push, pop, and modify.
>
> Also included are tests for the new funtionality. Note that these will
> require iproute2 changes to be submitted soon.
>
> NOTE: these patches are applied to net-next along with the patch:
> [PATCH net 1/1] net: openvswitch: fix csum updates for MPLS actions
> This patch has been accepted into net but, at time of posting, is not yet
> in net-next.
...
Thanks for mentioning that dependency.
Series applied to net-next, thank you.
prev parent reply other threads:[~2019-07-09 3:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-07 14:01 [PATCH net-next v7 0/5] Add MPLS actions to TC John Hurley
2019-07-07 14:01 ` [PATCH net-next v7 1/5] net: core: move push MPLS functionality from OvS to core helper John Hurley
2019-07-07 14:01 ` [PATCH net-next v7 2/5] net: core: move pop " John Hurley
2019-07-07 14:01 ` [PATCH net-next v7 3/5] net: core: add MPLS update core helper and use in OvS John Hurley
2019-07-07 14:01 ` [PATCH net-next v7 4/5] net: sched: add mpls manipulation actions to TC John Hurley
2019-07-07 14:01 ` [PATCH net-next v7 5/5] tc-tests: actions: add MPLS tests John Hurley
2019-07-09 3:05 ` David Miller [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=20190708.200509.2125973923907133864.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=dsahern@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@mellanox.com \
--cc=john.hurley@netronome.com \
--cc=mrv@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=simon.horman@netronome.com \
--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).