From: patchwork-bot+netdevbpf@kernel.org
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, leon@kernel.org,
michal.simek@xilinx.com, john.linn@xilinx.com,
sadanan@xilinx.com, linux-arm-kernel@lists.infradead.org,
yanok@emcraft.com, jreuter@yaina.de, linux-hams@vger.kernel.org
Subject: Re: [PATCH net v3 0/4] net: don't call dev_kfree_skb() under spin_lock_irqsave()
Date: Mon, 12 Dec 2022 10:10:16 +0000 [thread overview]
Message-ID: <167083981658.16910.12851344633864662339.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221208142147.2376671-1-yangyingliang@huawei.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 8 Dec 2022 22:21:43 +0800 you wrote:
> It is not allowed to call consume_skb() from hardware interrupt context
> or with interrupts being disabled. This patchset replace dev_kfree_skb()
> with dev_kfree_skb_irq/dev_consume_skb_irq() under spin_lock_irqsave()
> in some drivers, or move dev_kfree_skb() after spin_unlock_irqrestore().
>
> v2 -> v3:
> Update commit message, and change to use dev_kfree_skb_irq() in patch #1, #3.
>
> [...]
Here is the summary with links:
- [net,v3,1/4] net: emaclite: don't call dev_kfree_skb() under spin_lock_irqsave()
https://git.kernel.org/netdev/net/c/d1678bf45f21
- [net,v3,2/4] net: ethernet: dnet: don't call dev_kfree_skb() under spin_lock_irqsave()
https://git.kernel.org/netdev/net/c/f07fadcbee2a
- [net,v3,3/4] hamradio: don't call dev_kfree_skb() under spin_lock_irqsave()
https://git.kernel.org/netdev/net/c/3727f742915f
- [net,v3,4/4] net: amd: lance: don't call dev_kfree_skb() under spin_lock_irqsave()
https://git.kernel.org/netdev/net/c/6151d105dfce
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:[~2022-12-12 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 14:21 [PATCH net v3 0/4] net: don't call dev_kfree_skb() under spin_lock_irqsave() Yang Yingliang
2022-12-08 14:21 ` [PATCH net v3 3/4] hamradio: " Yang Yingliang
2022-12-12 10:10 ` 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=167083981658.16910.12851344633864662339.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=john.linn@xilinx.com \
--cc=jreuter@yaina.de \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hams@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sadanan@xilinx.com \
--cc=yangyingliang@huawei.com \
--cc=yanok@emcraft.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 read-only IMAP folder(s) and NNTP newsgroup(s).