From: Moshe Shemesh <moshe@mellanox.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
David Ahern <dsahern@gmail.com>
Cc: Jiri Pirko <jiri@mellanox.com>,
netdev@vger.kernel.org, Moshe Shemesh <moshe@mellanox.com>
Subject: [PATCH iproute2-next 0/3] devlink: Add devlink port health command
Date: Sun, 19 Jul 2020 16:36:00 +0300 [thread overview]
Message-ID: <1595165763-13657-1-git-send-email-moshe@mellanox.com> (raw)
Implement commands for interaction with per-port devlink health
reporters. To do this, adapt devlink-health for usage of port handles
with any existing devlink-health subcommands. Add devlink-port health
subcommand as an alias for devlink-health.
Vladyslav Tarasiuk (3):
devlink: Add a possibility to print arrays of devlink port handles
devlink: Add devlink port health command
devlink: Update devlink-health and devlink-port manpages
devlink/devlink.c | 94 +++++++++++++++++++++++++++++++++++----------
man/man8/devlink-health.8 | 84 ++++++++++++++++++++++++++++-----------
man/man8/devlink-port.8 | 19 +++++++++
3 files changed, 152 insertions(+), 45 deletions(-)
next reply other threads:[~2020-07-19 13:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 13:36 Moshe Shemesh [this message]
2020-07-19 13:36 ` [PATCH iproute2-next 1/3] devlink: Add a possibility to print arrays of devlink port handles Moshe Shemesh
2020-07-20 16:44 ` David Ahern
2020-07-20 16:58 ` David Ahern
2020-07-19 13:36 ` [PATCH iproute2-next 2/3] devlink: Add devlink port health command Moshe Shemesh
2020-07-19 13:36 ` [PATCH iproute2-next 3/3] devlink: Update devlink-health and devlink-port manpages Moshe Shemesh
2020-07-23 0:35 ` [PATCH iproute2-next 0/3] devlink: Add devlink port health command David Ahern
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=1595165763-13657-1-git-send-email-moshe@mellanox.com \
--to=moshe@mellanox.com \
--cc=dsahern@gmail.com \
--cc=jiri@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).