From: Simon Horman <horms@kernel•org>
To: Mateusz Polchlopek <mateusz.polchlopek@intel•com>
Cc: intel-wired-lan@lists•osuosl.org, apw@canonical•com,
joe@perches•com, dwaipayanray1@gmail•com,
lukas.bulwahn@gmail•com, akpm@linux-foundation•org,
willemb@google•com, edumazet@google•com,
linux-kernel@vger•kernel.org, netdev@vger•kernel.org,
Ben Shelton <benjamin.h.shelton@intel•com>,
Przemek Kitszel <przemyslaw.kitszel@intel•com>,
Igor Bagnucki <igor.bagnucki@intel•com>,
Wojciech Drewek <wojciech.drewek@intel•com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v1 5/6] ice: Add MDD logging via devlink health
Date: Mon, 8 Jul 2024 13:42:08 +0100 [thread overview]
Message-ID: <20240708124208.GR1481495@kernel.org> (raw)
In-Reply-To: <20240703125922.5625-6-mateusz.polchlopek@intel.com>
On Wed, Jul 03, 2024 at 08:59:21AM -0400, Mateusz Polchlopek wrote:
> From: Ben Shelton <benjamin.h.shelton@intel•com>
>
> Add a devlink health reporter for MDD events. The 'dump' handler will
> return the information captured in each call to ice_handle_mdd_event().
> A device reset (CORER/PFR) will put the reporter back in healthy state.
>
> Signed-off-by: Ben Shelton <benjamin.h.shelton@intel•com>
> Co-developed-by: Przemek Kitszel <przemyslaw.kitszel@intel•com>
> Signed-off-by: Przemek Kitszel <przemyslaw.kitszel@intel•com>
> Reviewed-by: Igor Bagnucki <igor.bagnucki@intel•com>
> Reviewed-by: Wojciech Drewek <wojciech.drewek@intel•com>
> Signed-off-by: Mateusz Polchlopek <mateusz.polchlopek@intel•com>
Reviewed-by: Simon Horman <horms@kernel•org>
next prev parent reply other threads:[~2024-07-08 12:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 12:59 [Intel-wired-lan] [PATCH iwl-next v1 0/6] Add support for devlink health events Mateusz Polchlopek
2024-07-03 12:59 ` [Intel-wired-lan] [PATCH iwl-next v1 1/6] checkpatch: don't complain on _Generic() use Mateusz Polchlopek
2024-07-08 12:41 ` Simon Horman
2024-07-03 12:59 ` [Intel-wired-lan] [PATCH iwl-next v1 2/6] devlink: add devlink_fmsg_put() macro Mateusz Polchlopek
2024-07-08 12:41 ` Simon Horman
2024-07-03 12:59 ` [Intel-wired-lan] [PATCH iwl-next v1 3/6] ice: add Tx hang devlink health reporter Mateusz Polchlopek
2024-07-05 0:23 ` kernel test robot
2024-07-08 12:40 ` Simon Horman
2024-07-10 13:59 ` Przemek Kitszel
2024-07-03 12:59 ` [Intel-wired-lan] [PATCH iwl-next v1 4/6] ice: print ethtool stats as part of " Mateusz Polchlopek
2024-07-08 12:41 ` Simon Horman
2024-07-03 12:59 ` [Intel-wired-lan] [PATCH iwl-next v1 5/6] ice: Add MDD logging via devlink health Mateusz Polchlopek
2024-07-08 12:42 ` Simon Horman [this message]
2024-07-03 12:59 ` [Intel-wired-lan] [PATCH iwl-next v1 6/6] ice: devlink health: dump also skb on Tx hang Mateusz Polchlopek
2024-07-08 12:42 ` Simon Horman
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=20240708124208.GR1481495@kernel.org \
--to=horms@kernel$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=apw@canonical$(echo .)com \
--cc=benjamin.h.shelton@intel$(echo .)com \
--cc=dwaipayanray1@gmail$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=igor.bagnucki@intel$(echo .)com \
--cc=intel-wired-lan@lists$(echo .)osuosl.org \
--cc=joe@perches$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=lukas.bulwahn@gmail$(echo .)com \
--cc=mateusz.polchlopek@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=przemyslaw.kitszel@intel$(echo .)com \
--cc=willemb@google$(echo .)com \
--cc=wojciech.drewek@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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