From: Jakub Kicinski <kuba@kernel.org>
To: Kamal Heib <kheib@redhat.com>
Cc: Ivan Vecera <ivecera@redhat.com>,
netdev@vger.kernel.org, Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
intel-wired-lan@lists.osuosl.org, Paolo Abeni <pabeni@redhat.com>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v2] i40e: Add support for fw health report
Date: Tue, 23 Jul 2024 10:36:44 -0700 [thread overview]
Message-ID: <20240723103644.1fea5124@kernel.org> (raw)
In-Reply-To: <20240718181319.145884-1-kheib@redhat.com>
On Thu, 18 Jul 2024 14:13:19 -0400 Kamal Heib wrote:
> Add support for reporting fw status via the devlink health report.
>
> Example:
> # devlink health show pci/0000:02:00.0 reporter fw
> pci/0000:02:00.0:
> reporter fw
> state healthy error 0 recover 0
> # devlink health diagnose pci/0000:02:00.0 reporter fw
> Mode: normal
I'm not sure if health reporter is the right fit, depends on what
the recovery mode is / does. We need documentation.
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Kamal Heib <kheib@redhat.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Ivan Vecera <ivecera@redhat.com>,
"David S . Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH iwl-next v2] i40e: Add support for fw health report
Date: Tue, 23 Jul 2024 10:36:44 -0700 [thread overview]
Message-ID: <20240723103644.1fea5124@kernel.org> (raw)
In-Reply-To: <20240718181319.145884-1-kheib@redhat.com>
On Thu, 18 Jul 2024 14:13:19 -0400 Kamal Heib wrote:
> Add support for reporting fw status via the devlink health report.
>
> Example:
> # devlink health show pci/0000:02:00.0 reporter fw
> pci/0000:02:00.0:
> reporter fw
> state healthy error 0 recover 0
> # devlink health diagnose pci/0000:02:00.0 reporter fw
> Mode: normal
I'm not sure if health reporter is the right fit, depends on what
the recovery mode is / does. We need documentation.
next prev parent reply other threads:[~2024-07-23 17:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 18:13 [Intel-wired-lan] [PATCH iwl-next v2] i40e: Add support for fw health report Kamal Heib
2024-07-18 18:13 ` Kamal Heib
2024-07-18 19:57 ` [Intel-wired-lan] " Paul Menzel
2024-07-18 19:57 ` Paul Menzel
2024-07-23 17:36 ` Jakub Kicinski [this message]
2024-07-23 17:36 ` Jakub Kicinski
2024-07-23 20:41 ` [Intel-wired-lan] " Brett Creeley
2024-07-23 20:41 ` Brett Creeley
2024-07-23 21:17 ` [Intel-wired-lan] " Keller, Jacob E
2024-07-23 21:17 ` Keller, Jacob E
2024-07-29 12:04 ` [Intel-wired-lan] " Przemek Kitszel
2024-07-29 12:04 ` Przemek Kitszel
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=20240723103644.1fea5124@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivecera@redhat.com \
--cc=kheib@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.