From: Eran Ben Elisha <eranbe@mellanox.com>
To: netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
Jiri Pirko <jiri@mellanox.com>,
Michael Chan <michael.chan@broadcom.com>,
"David S. Miller" <davem@davemloft.net>,
Saeed Mahameed <saeedm@mellanox.com>
Cc: Eran Ben Elisha <eranbe@mellanox.com>
Subject: [PATCH net-next 0/2] Devlink health auto attributes refactor
Date: Wed, 25 Mar 2020 15:26:22 +0200 [thread overview]
Message-ID: <1585142784-10517-1-git-send-email-eranbe@mellanox.com> (raw)
This patchset refactors the auto-recover health reporter flag to be
explicitly set by the devlink core.
In addition, add another flag to control auto-dump attribute, also
to be explicitly set by the devlink core.
After reporter registration, both flags can be altered be administrator
only.
Eran Ben Elisha (2):
devlink: Implicitly set auto recover flag when registering health
reporter
devlink: Add auto dump flag to health reporter
.../net/ethernet/broadcom/bnxt/bnxt_devlink.c | 6 ++--
.../mellanox/mlx5/core/en/reporter_rx.c | 2 +-
.../mellanox/mlx5/core/en/reporter_tx.c | 2 +-
.../net/ethernet/mellanox/mlx5/core/health.c | 4 +--
drivers/net/netdevsim/health.c | 4 +--
include/net/devlink.h | 3 +-
include/uapi/linux/devlink.h | 2 ++
net/core/devlink.c | 35 +++++++++++++------
8 files changed, 37 insertions(+), 21 deletions(-)
--
2.17.1
next reply other threads:[~2020-03-25 13:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 13:26 Eran Ben Elisha [this message]
2020-03-25 13:26 ` [PATCH net-next 1/2] devlink: Implicitly set auto recover flag when registering health reporter Eran Ben Elisha
2020-03-25 18:33 ` Jakub Kicinski
2020-03-25 13:26 ` [PATCH net-next 2/2] devlink: Add auto dump flag to " Eran Ben Elisha
2020-03-25 18:45 ` Jakub Kicinski
2020-03-25 19:08 ` Jiri Pirko
2020-03-25 19:38 ` Eran Ben Elisha
2020-03-26 0:01 ` Jakub Kicinski
2020-03-26 9:06 ` Eran Ben Elisha
2020-03-26 10:22 ` Jiri Pirko
2020-03-26 17:39 ` Jakub Kicinski
2020-03-26 21:23 ` Jiri Pirko
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=1585142784-10517-1-git-send-email-eranbe@mellanox.com \
--to=eranbe@mellanox.com \
--cc=davem@davemloft.net \
--cc=jiri@mellanox.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.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