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 0/3] ionic: PCI error handling fixes
Date: Tue, 27 Feb 2024 12:20:28 +0000 [thread overview]
Message-ID: <170903642882.13677.3100305220509387658.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240223222742.13923-1-shannon.nelson@amd.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 23 Feb 2024 14:27:39 -0800 you wrote:
> These are a few things to make our PCI reset handling better.
>
> Shannon Nelson (3):
> ionic: check before releasing pci regions
> ionic: check cmd_regs before copying in or out
> ionic: restore netdev feature bits after reset
>
> [...]
Here is the summary with links:
- [net,1/3] ionic: check before releasing pci regions
https://git.kernel.org/netdev/net/c/a36b0787f074
- [net,2/3] ionic: check cmd_regs before copying in or out
https://git.kernel.org/netdev/net/c/7662fad348ac
- [net,3/3] ionic: restore netdev feature bits after reset
https://git.kernel.org/netdev/net/c/155a1efc9b96
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:[~2024-02-27 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 22:27 [PATCH net 0/3] ionic: PCI error handling fixes Shannon Nelson
2024-02-23 22:27 ` [PATCH net 1/3] ionic: check before releasing pci regions Shannon Nelson
2024-02-23 22:27 ` [PATCH net 2/3] ionic: check cmd_regs before copying in or out Shannon Nelson
2024-02-23 22:27 ` [PATCH net 3/3] ionic: restore netdev feature bits after reset Shannon Nelson
2024-02-27 12:20 ` 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=170903642882.13677.3100305220509387658.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 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).