From: patchwork-bot+netdevbpf@kernel.org
To: Can Peng <pengcan@kylinos.cn>
Cc: manishc@marvell.com, rahulv@marvell.com,
GR-Linux-NIC-Dev@marvell.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] qlogic: fix and tidy notifier cleanup paths
Date: Mon, 03 Aug 2026 23:30:09 +0000 [thread overview]
Message-ID: <178579980913.2876283.149168107924184802.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260728032046.121631-1-pengcan@kylinos.cn>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 28 Jul 2026 11:20:44 +0800 you wrote:
> Hi,
>
> This series fixes and tidies notifier cleanup in the qlogic Ethernet
> drivers.
>
> Patch 1 fixes netxen by unregistering the netdevice and inetaddr
> notifiers if pci_register_driver() fails. Without this, module init can
> return an error while leaving callbacks registered for a module that did
> not load successfully.
>
> [...]
Here is the summary with links:
- [1/2] netxen: unregister notifiers if PCI registration fails
https://git.kernel.org/netdev/net-next/c/e8aaf6ba33c7
- [2/2] qlcnic: move notifier error cleanup under CONFIG_INET
(no matching commit)
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:[~2026-08-03 23:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 3:20 [PATCH 0/2] qlogic: fix and tidy notifier cleanup paths Can Peng
2026-07-28 3:20 ` [PATCH 1/2] netxen: unregister notifiers if PCI registration fails Can Peng
2026-07-29 23:06 ` Jacob Keller
2026-07-28 3:20 ` [PATCH 2/2] qlcnic: move notifier error cleanup under CONFIG_INET Can Peng
2026-07-29 23:38 ` Jacob Keller
2026-08-03 23:22 ` Jakub Kicinski
2026-08-03 23:30 ` 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=178579980913.2876283.149168107924184802.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pengcan@kylinos.cn \
--cc=rahulv@marvell.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