From: patchwork-bot+netdevbpf@kernel.org
To: Lorenzo Bianconi <lorenzo.bianconi@oss.qualcomm.com>
Cc: maxime.chevallier@bootlin.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net-next v3] net: stmmac: drop the queue-0 pinning for GSO frames
Date: Thu, 03 Sep 2026 10:10:06 +0000 [thread overview]
Message-ID: <178843020640.3244835.6785391854454806070.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260831-stmmac_select_queue-tso-fix-v3-1-d9c215fe7a85@oss.qualcomm.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 31 Aug 2026 08:48:33 +0200 you wrote:
> stmmac_select_queue() forces every GSO frame (TCPv4/TCPv6/UDP-L4) onto
> TX queue 0, relying on the legacy assumption that at least queue 0 is
> always TSO/USO capable. This is no longer needed since
> stmmac_features_check() already validates each GSO frame against the
> capabilities of the queue it is mapped to, clearing the checksum and GSO
> features for queues that cannot perform TSO (e.g. TBS queues or queues
> without TX checksum offload support).
>
> [...]
Here is the summary with links:
- [net-next,v3] net: stmmac: drop the queue-0 pinning for GSO frames
https://git.kernel.org/netdev/net-next/c/8e2faf945a13
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-03 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 6:48 [PATCH net-next v3] net: stmmac: drop the queue-0 pinning for GSO frames Lorenzo Bianconi
2026-09-02 18:48 ` [net-next,v3] " netdev-bot+sashiko
2026-09-02 21:21 ` Lorenzo Bianconi
2026-09-03 10:03 ` Paolo Abeni
2026-09-03 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=178843020640.3244835.6785391854454806070.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lorenzo.bianconi@oss.qualcomm.com \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.