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, andrew+netdev@lunn.ch,
jacob.e.keller@intel.com, brett.creeley@amd.com
Subject: Re: [PATCH v2 net 0/3] ionic: minor code fixes
Date: Sun, 15 Dec 2024 23:10:29 +0000 [thread overview]
Message-ID: <173430422978.3600507.1832286855650030183.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241212213157.12212-1-shannon.nelson@amd.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 12 Dec 2024 13:31:54 -0800 you wrote:
> These are a couple of code fixes for the ionic driver.
>
> Brett Creeley (1):
> ionic: Fix netdev notifier unregister on failure
>
> Shannon Nelson (2):
> ionic: no double destroy workqueue
> ionic: use ee->offset when returning sprom data
>
> [...]
Here is the summary with links:
- [v2,net,1/3] ionic: Fix netdev notifier unregister on failure
https://git.kernel.org/netdev/net/c/9590d32e090e
- [v2,net,2/3] ionic: no double destroy workqueue
https://git.kernel.org/netdev/net/c/746e6ae2e202
- [v2,net,3/3] ionic: use ee->offset when returning sprom data
https://git.kernel.org/netdev/net/c/b096d62ba132
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-12-15 23:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 21:31 [PATCH v2 net 0/3] ionic: minor code fixes Shannon Nelson
2024-12-12 21:31 ` [PATCH v2 net 1/3] ionic: Fix netdev notifier unregister on failure Shannon Nelson
2024-12-12 21:31 ` [PATCH v2 net 2/3] ionic: no double destroy workqueue Shannon Nelson
2024-12-12 21:31 ` [PATCH v2 net 3/3] ionic: use ee->offset when returning sprom data Shannon Nelson
2024-12-12 23:34 ` [PATCH v2 net 0/3] ionic: minor code fixes Jacob Keller
2024-12-15 23:10 ` 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=173430422978.3600507.1832286855650030183.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.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.