From: Simon Horman <horms@kernel.org>
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
Subject: Re: [PATCH net 0/5] pds_core: error handling fixes
Date: Fri, 25 Aug 2023 13:47:06 +0200 [thread overview]
Message-ID: <20230825114706.GN3523530@kernel.org> (raw)
In-Reply-To: <20230824161754.34264-1-shannon.nelson@amd.com>
On Thu, Aug 24, 2023 at 09:17:49AM -0700, Shannon Nelson wrote:
> Some fixes for better handling of broken states.
>
> Shannon Nelson (5):
> pds_core: protect devlink callbacks from fw_down state
> pds_core: no health reporter in VF
> pds_core: no reset command for VF
> pds_core: check for work queue before use
> pds_core: pass opcode to devcmd_wait
>
> drivers/net/ethernet/amd/pds_core/core.c | 11 +++++++----
> drivers/net/ethernet/amd/pds_core/dev.c | 9 +++------
> drivers/net/ethernet/amd/pds_core/devlink.c | 3 +++
> 3 files changed, 13 insertions(+), 10 deletions(-)
For series,
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2023-08-25 11:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 16:17 [PATCH net 0/5] pds_core: error handling fixes Shannon Nelson
2023-08-24 16:17 ` [PATCH net 1/5] pds_core: protect devlink callbacks from fw_down state Shannon Nelson
2023-08-24 16:17 ` [PATCH net 2/5] pds_core: no health reporter in VF Shannon Nelson
2023-08-24 16:17 ` [PATCH net 3/5] pds_core: no reset command for VF Shannon Nelson
2023-08-24 16:17 ` [PATCH net 4/5] pds_core: check for work queue before use Shannon Nelson
2023-08-24 16:17 ` [PATCH net 5/5] pds_core: pass opcode to devcmd_wait Shannon Nelson
2023-08-25 11:47 ` Simon Horman [this message]
2023-08-26 2:10 ` [PATCH net 0/5] pds_core: error handling fixes patchwork-bot+netdevbpf
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=20230825114706.GN3523530@kernel.org \
--to=horms@kernel.org \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=drivers@pensando.io \
--cc=kuba@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;
as well as URLs for NNTP newsgroup(s).