From: patchwork-bot+netdevbpf@kernel.org
To: G@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Thomas@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Rohan <rohan.g.thomas@altera.com>
Cc: 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, Jose.Abreu@synopsys.com,
rohan.g.thomas@intel.com, boon.khai.ng@altera.com,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, matthew.gerlach@altera.com
Subject: Re: [PATCH net v4 0/3] net: stmmac: Fixes for stmmac Tx VLAN insert and EST
Date: Thu, 30 Oct 2025 02:00:11 +0000 [thread overview]
Message-ID: <176178961100.3282477.1158388762703076399.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251028-qbv-fixes-v4-0-26481c7634e3@altera.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 28 Oct 2025 11:18:42 +0800 you wrote:
> This patchset includes following fixes for stmmac Tx VLAN insert and
> EST implementations:
> 1. Disable STAG insertion offloading, as DWMAC IPs doesn't support
> offload of STAG for double VLAN packets and CTAG for single VLAN
> packets when using the same register configuration. The current
> configuration in the driver is undocumented and is adding an
> additional 802.1Q tag with VLAN ID 0 for double VLAN packets.
> 2. Consider Tx VLAN offload tag length for maxSDU estimation.
> 3. Fix GCL bounds check
>
> [...]
Here is the summary with links:
- [net,v4,1/3] net: stmmac: vlan: Disable 802.1AD tag insertion offload
https://git.kernel.org/netdev/net/c/c657f86106c8
- [net,v4,2/3] net: stmmac: Consider Tx VLAN offload tag length for maxSDU
https://git.kernel.org/netdev/net/c/ded9813d17d3
- [net,v4,3/3] net: stmmac: est: Fix GCL bounds checks
https://git.kernel.org/netdev/net/c/48b2e323c018
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-10-30 2:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 3:18 [PATCH net v4 0/3] net: stmmac: Fixes for stmmac Tx VLAN insert and EST Rohan G Thomas via B4 Relay
2025-10-28 3:18 ` [PATCH net v4 1/3] net: stmmac: vlan: Disable 802.1AD tag insertion offload Rohan G Thomas via B4 Relay
2025-10-28 3:18 ` [PATCH net v4 2/3] net: stmmac: Consider Tx VLAN offload tag length for maxSDU Rohan G Thomas via B4 Relay
2025-10-28 3:18 ` [PATCH net v4 3/3] net: stmmac: est: Fix GCL bounds checks Rohan G Thomas via B4 Relay
2025-10-30 2:00 ` 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=176178961100.3282477.1158388762703076399.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=G@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=Jose.Abreu@synopsys.com \
--cc=Thomas@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=boon.khai.ng@altera.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=matthew.gerlach@altera.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rohan.g.thomas@altera.com \
--cc=rohan.g.thomas@intel.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