From: patchwork-bot+netdevbpf@kernel.org
To: Dawei Li <dawei.li@shingroup.cn>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, ioana.ciornei@nxp.com, wintera@linux.ibm.com,
twinkler@linux.ibm.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] Avoid explicit cpumask var allocation on stack
Date: Wed, 03 Apr 2024 01:40:34 +0000 [thread overview]
Message-ID: <171210843497.14193.16578910884878610890.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240331053441.1276826-1-dawei.li@shingroup.cn>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 31 Mar 2024 13:34:39 +0800 you wrote:
> Hi,
>
> This is v2 of previous series[1] about cpumask var on stack for net
> subsystem.
>
> Change since v1:
> - For iucv_setmask_up() which returns void to caller, just make cpumask
> var static which is protected by global lock iucv_register_mutex. [Eric]
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net/iucv: Avoid explicit cpumask var allocation on stack
https://git.kernel.org/netdev/net-next/c/be4e1304419c
- [net-next,v2,2/2] net/dpaa2: Avoid explicit cpumask var allocation on stack
https://git.kernel.org/netdev/net-next/c/d33fe1714a44
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-04-03 1:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 5:34 [PATCH net-next v2 0/2] Avoid explicit cpumask var allocation on stack Dawei Li
2024-03-31 5:34 ` Dawei Li
2024-03-31 5:34 ` [PATCH net-next v2 1/2] net/iucv: " Dawei Li
2024-03-31 5:34 ` Dawei Li
2024-04-02 12:41 ` Alexandra Winter
2024-03-31 5:34 ` [PATCH net-next v2 2/2] net/dpaa2: " Dawei Li
2024-03-31 5:34 ` Dawei Li
2024-04-03 1: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=171210843497.14193.16578910884878610890.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dawei.li@shingroup.cn \
--cc=edumazet@google.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=twinkler@linux.ibm.com \
--cc=wintera@linux.ibm.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