From: patchwork-bot+netdevbpf@kernel.org
To: Jianbo Liu <jianbol@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, jv@jvosburgh.net,
andy@greyhouse.net, saeedm@nvidia.com, gal@nvidia.com,
leonro@nvidia.com, liuhangbin@gmail.com, tariqt@nvidia.com
Subject: Re: [PATCH net V6 0/3] Fixes for IPsec over bonding
Date: Tue, 27 Aug 2024 20:20:30 +0000 [thread overview]
Message-ID: <172479003002.753271.9461945323497406231.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240823031056.110999-1-jianbol@nvidia.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 23 Aug 2024 06:10:53 +0300 you wrote:
> Hi,
>
> This patchset provides bug fixes for IPsec over bonding driver.
>
> It adds the missing xdo_dev_state_free API, and fixes "scheduling while
> atomic" by using mutex lock instead.
>
> [...]
Here is the summary with links:
- [net,V6,1/3] bonding: implement xdo_dev_state_free and call it after deletion
https://git.kernel.org/netdev/net/c/ec13009472f4
- [net,V6,2/3] bonding: extract the use of real_device into local variable
https://git.kernel.org/netdev/net/c/907ed83a7583
- [net,V6,3/3] bonding: change ipsec_lock from spin lock to mutex
https://git.kernel.org/netdev/net/c/2aeeef906d5a
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-08-27 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 3:10 [PATCH net V6 0/3] Fixes for IPsec over bonding Jianbo Liu
2024-08-23 3:10 ` [PATCH net V6 1/3] bonding: implement xdo_dev_state_free and call it after deletion Jianbo Liu
2024-08-23 3:10 ` [PATCH net V6 2/3] bonding: extract the use of real_device into local variable Jianbo Liu
2024-08-23 3:10 ` [PATCH net V6 3/3] bonding: change ipsec_lock from spin lock to mutex Jianbo Liu
2024-08-23 20:33 ` [PATCH net V6 0/3] Fixes for IPsec over bonding Jay Vosburgh
2024-08-27 20: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=172479003002.753271.9461945323497406231.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=jianbol@nvidia.com \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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).