From: patchwork-bot+netdevbpf@kernel.org
To: Simon Horman <simon.horman@corigine.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
steffen.klassert@secunet.com, herbert@gondor.apana.org.au,
leon@kernel.org, chengtian.liu@corigine.com,
yinjun.zhang@corigine.com, niklas.soderlund@corigine.com,
netdev@vger.kernel.org, oss-drivers@corigine.com
Subject: Re: [PATCH net 0/2] nfp: fix schedule in atomic context when offloading sa
Date: Fri, 10 Feb 2023 06:40:18 +0000 [thread overview]
Message-ID: <167601121820.3411.4468929497546422008.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230208102258.29639-1-simon.horman@corigine.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 8 Feb 2023 11:22:56 +0100 you wrote:
> Yinjun Zhang says:
>
> IPsec offloading callbacks may be called in atomic context, sleep is
> not allowed in the implementation. Now use workqueue mechanism to
> avoid this issue.
>
> Extend existing workqueue mechanism for multicast configuration only
> to universal use, so that all configuring through mailbox asynchoronously
> can utilize it.
>
> [...]
Here is the summary with links:
- [net,1/2] nfp: fix incorrect use of mbox in IPsec code
https://git.kernel.org/netdev/net/c/7a13a2eef645
- [net,2/2] nfp: fix schedule in atomic context when offloading sa
https://git.kernel.org/netdev/net/c/71f814cda659
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:[~2023-02-10 6:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 10:22 [PATCH net 0/2] nfp: fix schedule in atomic context when offloading sa Simon Horman
2023-02-08 10:22 ` [PATCH net 1/2] nfp: fix incorrect use of mbox in IPsec code Simon Horman
2023-02-08 10:22 ` [PATCH net 2/2] nfp: fix schedule in atomic context when offloading sa Simon Horman
2023-02-10 6:40 ` 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=167601121820.3411.4468929497546422008.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=chengtian.liu@corigine.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.com \
--cc=steffen.klassert@secunet.com \
--cc=yinjun.zhang@corigine.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.