From: David Ahern <dsahern@gmail.com>
To: Ido Schimmel <idosch@idosch.org>, netdev@vger.kernel.org
Cc: dsahern@gmail.com, stephen@networkplumber.org, jiri@mellanox.com,
mlxsw@mellanox.com, Ido Schimmel <idosch@mellanox.com>
Subject: Re: [PATCH iproute2-next v2 0/3] Add devlink-trap policers support
Date: Tue, 31 Mar 2020 17:27:54 -0600 [thread overview]
Message-ID: <7d011e0e-14b8-fe7f-7ac5-16cc6e4fc6b0@gmail.com> (raw)
In-Reply-To: <20200331084253.2377588-1-idosch@idosch.org>
On 3/31/20 2:42 AM, Ido Schimmel wrote:
> From: Ido Schimmel <idosch@mellanox.com>
>
> This patch set adds devlink-trap policers support in iproute2.
>
> Patch #1 adds devlink trap policer set and show commands.
>
> Patch #2 adds ability to bind a policer to a trap group.
>
> Patch #3 adds bash completion for new commands.
>
> See individual commit messages for example usage and output.
>
> v2:
> * Add patch #3
>
> Ido Schimmel (3):
> devlink: Add devlink trap policer set and show commands
> devlink: Add ability to bind policer to trap group
> bash-completion: devlink: Extend bash-completion for new commands
>
> bash-completion/devlink | 131 +++++++++++++++++++++++++-
> devlink/devlink.c | 185 ++++++++++++++++++++++++++++++++++++-
> man/man8/devlink-monitor.8 | 2 +-
> man/man8/devlink-trap.8 | 52 +++++++++++
> 4 files changed, 365 insertions(+), 5 deletions(-)
>
applied to iproute2-next. Thanks
prev parent reply other threads:[~2020-03-31 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 8:42 [PATCH iproute2-next v2 0/3] Add devlink-trap policers support Ido Schimmel
2020-03-31 8:42 ` [PATCH iproute2-next v2 1/3] devlink: Add devlink trap policer set and show commands Ido Schimmel
2020-03-31 8:42 ` [PATCH iproute2-next v2 2/3] devlink: Add ability to bind policer to trap group Ido Schimmel
2020-03-31 8:42 ` [PATCH iproute2-next v2 3/3] bash-completion: devlink: Extend bash-completion for new commands Ido Schimmel
2020-03-31 23:27 ` 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=7d011e0e-14b8-fe7f-7ac5-16cc6e4fc6b0@gmail.com \
--to=dsahern@gmail.com \
--cc=idosch@idosch.org \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=mlxsw@mellanox.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).