From: Hangbin Liu <liuhangbin@gmail.com>
To: Tariq Toukan <tariqt@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Jay Vosburgh <jv@jvosburgh.net>,
Andy Gospodarek <andy@greyhouse.net>,
netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>,
Gal Pressman <gal@nvidia.com>,
Leon Romanovsky <leonro@nvidia.com>
Subject: Re: [PATCH net 0/4] Fixes for IPsec over bonding
Date: Wed, 31 Jul 2024 11:20:36 +0800 [thread overview]
Message-ID: <ZqmthLxup5mYi6f2@Laptop-X1> (raw)
In-Reply-To: <20240729124406.1824592-1-tariqt@nvidia.com>
On Mon, Jul 29, 2024 at 03:44:01PM +0300, Tariq Toukan wrote:
> Hi,
>
> This patchset by Jianbo 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.
Good, I'm also working on the bonding IPsec offload issues recently. This save
some of my works :)
Hangbin
prev parent reply other threads:[~2024-07-31 3:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 12:44 [PATCH net 0/4] Fixes for IPsec over bonding Tariq Toukan
2024-07-29 12:44 ` [PATCH net 1/4] bonding: implement xfrm state xdo_dev_state_free API Tariq Toukan
2024-07-31 3:27 ` Hangbin Liu
2024-07-31 6:52 ` Jianbo Liu
2024-07-29 12:44 ` [PATCH net 2/4] bonding: call xfrm state xdo_dev_state_free after deletion Tariq Toukan
2024-07-31 3:36 ` Hangbin Liu
2024-07-31 7:08 ` Jianbo Liu
2024-07-29 12:44 ` [PATCH net 3/4] bonding: extract the use of real_device into local variable Tariq Toukan
2024-07-29 12:44 ` [PATCH net 4/4] bonding: change ipsec_lock from spin lock to mutex Tariq Toukan
2024-07-30 11:28 ` Paolo Abeni
2024-07-31 6:29 ` Jianbo Liu
2024-07-31 3:20 ` Hangbin Liu [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=ZqmthLxup5mYi6f2@Laptop-X1 \
--to=liuhangbin@gmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.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).