From: Jiri Pirko <jiri@resnulli.us>
To: Eran Ben Elisha <eranbe@mellanox.com>
Cc: netdev@vger.kernel.org, Jiri Pirko <jiri@mellanox.com>,
"David S. Miller" <davem@davemloft.net>,
Ariel Almog <ariela@mellanox.com>, Aya Levin <ayal@mellanox.com>,
Moshe Shemesh <moshe@mellanox.com>
Subject: Re: [PATCH net-next 00/27] Devlink health reporting and recovery system
Date: Thu, 17 Jan 2019 19:52:20 +0100 [thread overview]
Message-ID: <20190117185220.GK5265@nanopsycho> (raw)
In-Reply-To: <1547737521-29888-1-git-send-email-eranbe@mellanox.com>
Thu, Jan 17, 2019 at 04:04:54PM CET, eranbe@mellanox.com wrote:
27 patches is way too many to review in one go.
Please split to at least 2 patchsets. Thanks!
next prev parent reply other threads:[~2019-01-17 19:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 15:04 [PATCH net-next 00/27] Devlink health reporting and recovery system Eran Ben Elisha
2019-01-17 15:04 ` [PATCH net-next 01/27] devlink: Add health buffer support Eran Ben Elisha
2019-01-17 15:04 ` [PATCH net-next 02/27] devlink: Add health reporter create/destroy functionality Eran Ben Elisha
2019-01-17 15:04 ` [PATCH net-next 03/27] devlink: Add health report functionality Eran Ben Elisha
2019-01-17 15:04 ` [PATCH net-next 04/27] devlink: Add health get command Eran Ben Elisha
2019-01-17 15:04 ` [PATCH net-next 05/27] devlink: Add health set command Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 06/27] devlink: Add health recover command Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 07/27] devlink: Add health diagnose command Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 08/27] devlink: Add health dump {get,clear} commands Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 09/27] net/mlx5e: Add TX reporter support Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 10/27] net/mlx5e: Add TX timeout support for mlx5e TX reporter Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 11/27] net/mlx5: Move all devlink related functions calls to devlink.c Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 12/27] net/mlx5: Add Vendor Specific Capability access gateway Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 13/27] net/mlx5: Add Crdump FW snapshot support Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 14/27] net/mlx5: Use devlink region_snapshot parameter Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 15/27] Documentation: mlx5: Update kernel documentation Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 16/27] net/mlx5: Handle SW reset of FW in error flow Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 17/27] net/mlx5: Control CR-space access by different PFs Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 18/27] net/mlx5: Issue SW reset on FW assert Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 19/27] net/mlx5: Refactor print health info Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 20/27] net/mlx5: Create FW devlink_health_reporter Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 21/27] net/mlx5: Add core dump register access functions Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 22/27] net/mlx5: Add support for FW reporter dump Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 23/27] net/mlx5: Report devlink health on FW issues Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 24/27] net/mlx5: Add FW fatal devlink_health_reporter Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 25/27] net/mlx5: Add support for FW fatal reporter dump Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 26/27] net/mlx5: Report devlink health on FW fatal issues Eran Ben Elisha
2019-01-17 15:05 ` [PATCH net-next 27/27] devlink: Add Documentation/networking/devlink-health.txt Eran Ben Elisha
2019-01-17 15:09 ` [PATCH] devlink: Add health command support Aya Levin
2019-01-17 18:52 ` Jiri Pirko [this message]
2019-01-17 21:30 ` [PATCH net-next 00/27] Devlink health reporting and recovery system Eran Ben Elisha
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=20190117185220.GK5265@nanopsycho \
--to=jiri@resnulli.us \
--cc=ariela@mellanox.com \
--cc=ayal@mellanox.com \
--cc=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).