From: Stephen Hemminger <stephen@networkplumber.org>
To: Arkadi Sharshevsky <arkadis@mellanox.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, jiri@resnulli.us,
mlxsw@mellanox.com, andrew@lunn.ch
Subject: Re: [PATCH iproute2 0/4] Add support for dpipe's global header formatting
Date: Thu, 7 Sep 2017 15:13:23 -0700 [thread overview]
Message-ID: <20170907151323.74aecbdd@xeon-e3> (raw)
In-Reply-To: <1504794403-45690-1-git-send-email-arkadis@mellanox.com>
On Thu, 7 Sep 2017 17:26:39 +0300
Arkadi Sharshevsky <arkadis@mellanox.com> wrote:
> Some dpipe's global header values need special formatting, for example
> Ethernet and IP addresses. This patchset adds support for IPv4/6 and
> Ethernet's special format.
>
> Arkadi Sharshevsky (4):
> devlink: Make match/action parsing more flexible
> devlink: Add support for special format protocol headers
> devlink: Update devlink UAPI file
> devlink: Add support for protocol IPv4/IPv6/Ethernet special formats
>
> devlink/devlink.c | 319 +++++++++++++++++++++++++++++++++++++-----------
> include/linux/devlink.h | 18 +++
> 2 files changed, 265 insertions(+), 72 deletions(-)
>
Applied 1,2 and 4. #3 was not needed.
prev parent reply other threads:[~2017-09-07 22:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 14:26 [PATCH iproute2 0/4] Add support for dpipe's global header formatting Arkadi Sharshevsky
2017-09-07 14:26 ` [PATCH iproute2 1/4] devlink: Make match/action parsing more flexible Arkadi Sharshevsky
2017-09-07 14:26 ` [PATCH iproute2 2/4] devlink: Add support for special format protocol headers Arkadi Sharshevsky
2017-09-07 14:26 ` [PATCH iproute2 3/4] devlink: Update devlink UAPI file Arkadi Sharshevsky
2017-09-07 22:12 ` Stephen Hemminger
2017-09-07 14:26 ` [PATCH iproute2 4/4] devlink: Add support for protocol IPv4/IPv6/Ethernet special formats Arkadi Sharshevsky
2017-09-07 22:13 ` 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=20170907151323.74aecbdd@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=andrew@lunn.ch \
--cc=arkadis@mellanox.com \
--cc=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.