From: patchwork-bot+netdevbpf@kernel.org
To: Xuanqiang Luo <xuanqiang.luo@linux.dev>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
bigeasy@linutronix.de, dongchenchen2@huawei.com,
dsahern@kernel.org, luoxuanqiang@kylinos.cn, kees@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v1] net: gro_cells: add drop reasons to gro_cells_receive()
Date: Sun, 20 Sep 2026 00:30:06 +0000 [thread overview]
Message-ID: <178986420690.1502569.3136807848474973558.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260916091420.138170-1-xuanqiang.luo@linux.dev>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 16 Sep 2026 17:14:20 +0800 you wrote:
> From: Xuanqiang Luo <luoxuanqiang@kylinos.cn>
>
> gro_cells_receive() reports SKB_DROP_REASON_NOT_SPECIFIED when the device
> is down or the GRO cell queue length exceeds max_backlog.
>
> Pass SKB_DROP_REASON_DEV_READY and SKB_DROP_REASON_CPU_BACKLOG to
> kfree_skb_reason() for these two cases, respectively.
>
> [...]
Here is the summary with links:
- [net-next,v1] net: gro_cells: add drop reasons to gro_cells_receive()
https://git.kernel.org/netdev/net-next/c/a907a89ff105
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:[~2026-09-20 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 9:14 [PATCH net-next v1] net: gro_cells: add drop reasons to gro_cells_receive() Xuanqiang Luo
2026-09-16 9:29 ` Eric Dumazet
2026-09-20 0: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=178986420690.1502569.3136807848474973558.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=dongchenchen2@huawei.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luoxuanqiang@kylinos.cn \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xuanqiang.luo@linux.dev \
/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.