From: David Ahern <dsahern@gmail.com>
To: Aya Levin <ayal@mellanox.com>
Cc: netdev@vger.kernel.org, Jiri Pirko <jiri@mellanox.com>,
Moshe Shemesh <moshe@mellanox.com>,
Eran Ben Elisha <eranbe@mellanox.com>
Subject: Re: [PATCH v4 iproute2-next 00/11] Add support for devlink health
Date: Thu, 28 Feb 2019 09:01:39 -0700 [thread overview]
Message-ID: <5f754dda-a6f2-b97f-2e01-d9a55f323887@gmail.com> (raw)
In-Reply-To: <1551355984-15752-1-git-send-email-ayal@mellanox.com>
On 2/28/19 5:12 AM, Aya Levin wrote:
> This series adds support for devlink health commands:
> devlink health show [ DEV reporter REPORTER_NAME ]
> devlink health recover DEV reporter REPORTER_NAME
> devlink health diagnose DEV reporter REPORTER_NAME
> devlink health dump show DEV reporter REPORTER_NAME
> devlink health dump clear DEV reporter REPORTER_NAME
> devlink health set DEV reporter REPORTER_NAME { grace_period | auto_recover } { msec | boolean }
>
> The first patch refactors the validation of input parameters, which
> grow way too long. Second and third patches fix bugs that were
> discovered during the devlink health development. The forth patch adds
> helper functions which enable output of value and labels separately.
> Patches 5-10 add the devlink health functionality by command, the last
> is the man page.
>
applied to iproute2-next. Thanks
prev parent reply other threads:[~2019-02-28 16:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 12:12 [PATCH v4 iproute2-next 00/11] Add support for devlink health Aya Levin
2019-02-28 12:12 ` [PATCH v4 iproute2-next 01/11] devlink: Refactor validation of finding required arguments Aya Levin
2019-02-28 12:12 ` [PATCH v4 iproute2-next 02/11] devlink: Fix print of uint64_t Aya Levin
2019-02-28 12:12 ` [PATCH v4 iproute2-next 03/11] devlink: Fix boolean JSON print Aya Levin
2019-02-28 12:12 ` [PATCH v4 iproute2-next 04/11] devlink: Add helper functions for name and value separately Aya Levin
2019-02-28 12:12 ` [PATCH v4 iproute2-next 05/11] devlink: Add devlink health show command Aya Levin
2019-02-28 12:12 ` [PATCH v4 iproute2-next 06/11] devlink: Add devlink health recover command Aya Levin
2019-02-28 12:13 ` [PATCH v4 iproute2-next 07/11] devlink: Add devlink health diagnose command Aya Levin
2019-02-28 12:13 ` [PATCH v4 iproute2-next 08/11] devlink: Add devlink health dump show command Aya Levin
2019-02-28 12:13 ` [PATCH v4 iproute2-next 09/11] devlink: Add devlink health dump clear command Aya Levin
2019-02-28 12:13 ` [PATCH v4 iproute2-next 10/11] devlink: Add devlink health set command Aya Levin
2019-02-28 12:13 ` [PATCH v4 iproute2-next 11/11] devlink: Add devlink-health man page Aya Levin
2019-02-28 16:01 ` 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=5f754dda-a6f2-b97f-2e01-d9a55f323887@gmail.com \
--to=dsahern@gmail.com \
--cc=ayal@mellanox.com \
--cc=eranbe@mellanox.com \
--cc=jiri@mellanox.com \
--cc=moshe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox