From: patchwork-bot+netdevbpf@kernel.org
To: Shannon Nelson <shannon.nelson@amd.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, brett.creeley@amd.com,
drivers@pensando.io
Subject: Re: [PATCH net-next 0/8] ionic: updates to PCI error handling
Date: Wed, 13 Dec 2023 12:40:25 +0000 [thread overview]
Message-ID: <170247122552.30596.16162818098614293135.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231211185804.18668-1-shannon.nelson@amd.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 11 Dec 2023 10:57:56 -0800 you wrote:
> These are improvements to our PCI error handling, including FLR and
> AER events.
>
> Shannon Nelson (8):
> ionic: pass opcode to devcmd_wait
> ionic: keep filters across FLR
> ionic: bypass firmware cmds when stuck in reset
> ionic: prevent pci disable of already disabled device
> ionic: no fw read when PCI reset failed
> ionic: use timer_shutdown_sync
> ionic: lif debugfs refresh on reset
> ionic: fill out pci error handlers
>
> [...]
Here is the summary with links:
- [net-next,1/8] ionic: pass opcode to devcmd_wait
https://git.kernel.org/netdev/net-next/c/24f110240c03
- [net-next,2/8] ionic: keep filters across FLR
https://git.kernel.org/netdev/net-next/c/45b84188a0a4
- [net-next,3/8] ionic: bypass firmware cmds when stuck in reset
https://git.kernel.org/netdev/net-next/c/ca5fdf9a7c5b
- [net-next,4/8] ionic: prevent pci disable of already disabled device
https://git.kernel.org/netdev/net-next/c/13943d6c8273
- [net-next,5/8] ionic: no fw read when PCI reset failed
https://git.kernel.org/netdev/net-next/c/219e183272b4
- [net-next,6/8] ionic: use timer_shutdown_sync
https://git.kernel.org/netdev/net-next/c/b0dbe358fbb4
- [net-next,7/8] ionic: lif debugfs refresh on reset
https://git.kernel.org/netdev/net-next/c/ce66172d3393
- [net-next,8/8] ionic: fill out pci error handlers
https://git.kernel.org/netdev/net-next/c/c3a910e1c47a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-12-13 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 18:57 [PATCH net-next 0/8] ionic: updates to PCI error handling Shannon Nelson
2023-12-11 18:57 ` [PATCH net-next 1/8] ionic: pass opcode to devcmd_wait Shannon Nelson
2023-12-11 18:57 ` [PATCH net-next 2/8] ionic: keep filters across FLR Shannon Nelson
2023-12-11 18:57 ` [PATCH net-next 3/8] ionic: bypass firmware cmds when stuck in reset Shannon Nelson
2023-12-11 18:58 ` [PATCH net-next 4/8] ionic: prevent pci disable of already disabled device Shannon Nelson
2023-12-11 18:58 ` [PATCH net-next 5/8] ionic: no fw read when PCI reset failed Shannon Nelson
2023-12-11 18:58 ` [PATCH net-next 6/8] ionic: use timer_shutdown_sync Shannon Nelson
2023-12-11 18:58 ` [PATCH net-next 7/8] ionic: lif debugfs refresh on reset Shannon Nelson
2023-12-11 18:58 ` [PATCH net-next 8/8] ionic: fill out pci error handlers Shannon Nelson
2023-12-13 12:40 ` patchwork-bot+netdevbpf [this message]
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=170247122552.30596.16162818098614293135.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=drivers@pensando.io \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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 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.