From: patchwork-bot+netdevbpf@kernel.org
To: Frederic Weisbecker <frederic@kernel.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
leitao@debian.org, kuba@kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, romieu@fr.zoreil.com,
pmenzel@molgen.mpg.de, jdamato@fastly.com
Subject: Re: [PATCH net v2] net: Handle napi_schedule() calls from non-interrupt
Date: Thu, 27 Feb 2025 03:30:33 +0000 [thread overview]
Message-ID: <174062703399.955127.10228053973546865389.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250223221708.27130-1-frederic@kernel.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 23 Feb 2025 23:17:08 +0100 you wrote:
> napi_schedule() is expected to be called either:
>
> * From an interrupt, where raised softirqs are handled on IRQ exit
>
> * From a softirq disabled section, where raised softirqs are handled on
> the next call to local_bh_enable().
>
> [...]
Here is the summary with links:
- [net,v2] net: Handle napi_schedule() calls from non-interrupt
https://git.kernel.org/netdev/net/c/77e45145e303
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:[~2025-02-27 3:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-23 22:17 [PATCH net v2] net: Handle napi_schedule() calls from non-interrupt Frederic Weisbecker
2025-02-26 10:31 ` Eric Dumazet
2025-02-26 13:21 ` Frederic Weisbecker
2025-02-26 13:34 ` Eric Dumazet
2025-02-26 13:38 ` Frederic Weisbecker
2025-03-05 8:52 ` Sebastian Andrzej Siewior
2025-02-27 3:30 ` 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=174062703399.955127.10228053973546865389.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=frederic@kernel.org \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--cc=romieu@fr.zoreil.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