From: Jiri Pirko <jiri@resnulli.us>
To: Shannon Nelson <shannon.nelson@amd.com>
Cc: brett.creeley@amd.com, davem@davemloft.net,
netdev@vger.kernel.org, kuba@kernel.org, drivers@pensando.io,
leon@kernel.org
Subject: Re: [PATCH RFC v4 net-next 03/13] pds_core: health timer and workqueue
Date: Thu, 9 Mar 2023 10:30:14 +0100 [thread overview]
Message-ID: <ZAmnJvkAe4vJHRcN@nanopsycho> (raw)
In-Reply-To: <64d72af6-66f5-ff68-f7b3-1fffba61422b@amd.com>
Thu, Mar 09, 2023 at 03:08:44AM CET, shannon.nelson@amd.com wrote:
>On 3/8/23 1:39 AM, Jiri Pirko wrote:
>> Wed, Mar 08, 2023 at 06:13:00AM CET, shannon.nelson@amd.com wrote:
>> > Add in the periodic health check and the related workqueue,
>> > as well as the handlers for when a FW reset is seen.
>>
>> Why don't you use devlink health to let the user know that something odd
>> happened with HW?
>
>Just haven't gotten to that yet.
Please do it from start, this is exactly why devlink health was
introduced.
>sln
>
next prev parent reply other threads:[~2023-03-09 9:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 5:12 [PATCH RFC v4 net-next 00/13] pds_core driver Shannon Nelson
2023-03-08 5:12 ` [PATCH RFC v4 net-next 01/13] pds_core: initial framework for pds_core PF driver Shannon Nelson
2023-03-08 5:12 ` [PATCH RFC v4 net-next 02/13] pds_core: add devcmd device interfaces Shannon Nelson
2023-03-08 9:37 ` Jiri Pirko
2023-03-09 2:05 ` Shannon Nelson
2023-03-09 9:29 ` Jiri Pirko
2023-03-09 22:25 ` Shannon Nelson
2023-03-08 5:13 ` [PATCH RFC v4 net-next 03/13] pds_core: health timer and workqueue Shannon Nelson
2023-03-08 9:39 ` Jiri Pirko
2023-03-09 2:08 ` Shannon Nelson
2023-03-09 9:30 ` Jiri Pirko [this message]
2023-03-09 22:26 ` Shannon Nelson
2023-03-08 5:13 ` [PATCH RFC v4 net-next 04/13] pds_core: set up device and adminq Shannon Nelson
2023-03-08 5:13 ` [PATCH RFC v4 net-next 05/13] pds_core: Add adminq processing and commands Shannon Nelson
2023-03-08 5:13 ` [PATCH RFC v4 net-next 06/13] pds_core: add FW update feature to devlink Shannon Nelson
2023-03-08 5:13 ` [PATCH RFC v4 net-next 07/13] pds_core: set up the VIF definitions and defaults Shannon Nelson
2023-03-08 5:13 ` [PATCH RFC v4 net-next 08/13] pds_core: add initial VF device handling Shannon Nelson
2023-03-08 5:13 ` [PATCH RFC v4 net-next 09/13] pds_core: add auxiliary_bus devices Shannon Nelson
2023-03-08 5:13 ` [PATCH RFC v4 net-next 10/13] pds_core: devlink params for enabling VIF support Shannon Nelson
2023-03-08 5:13 ` [PATCH RFC v4 net-next 11/13] pds_core: add the aux client API Shannon Nelson
2023-03-14 12:14 ` Leon Romanovsky
2023-03-14 16:53 ` Shannon Nelson
2023-03-15 8:21 ` Leon Romanovsky
2023-03-16 1:08 ` Shannon Nelson
2023-03-08 5:13 ` [PATCH RFC v4 net-next 12/13] pds_core: publish events to the clients Shannon Nelson
2023-03-08 5:13 ` [PATCH RFC v4 net-next 13/13] pds_core: Kconfig and pds_core.rst Shannon Nelson
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=ZAmnJvkAe4vJHRcN@nanopsycho \
--to=jiri@resnulli.us \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=drivers@pensando.io \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@amd.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