From: patchwork-bot+netdevbpf@kernel.org
To: Clemens Gruber <mail@clemensgruber.at>
Cc: wei.fang@nxp.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
shenwei.wang@nxp.com, xiaoning.wang@nxp.com, imx@lists.linux.dev,
netdev@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH v2] net: fec: account for VLAN header in frame length calculations
Date: Thu, 22 Jan 2026 12:30:05 +0000 [thread overview]
Message-ID: <176908500535.1702959.10720487953177513534.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260121083751.66997-1-mail@clemensgruber.at>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 21 Jan 2026 09:37:51 +0100 you wrote:
> The MAX_FL (maximum frame length) and related calculations used ETH_HLEN,
> which does not account for the 4-byte VLAN tag in tagged frames. This
> caused the hardware to reject valid VLAN frames as oversized, resulting
> in RX errors and dropped packets.
>
> Use VLAN_ETH_HLEN instead of ETH_HLEN in the MAX_FL register setup,
> cut-through mode threshold, buffer allocation, and max_mtu calculation.
>
> [...]
Here is the summary with links:
- [v2] net: fec: account for VLAN header in frame length calculations
https://git.kernel.org/netdev/net/c/ca1bb3fedf26
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-01-22 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 16:04 [PATCH] net: fec: account for VLAN header in MAX_FL calculation Clemens Gruber
2026-01-21 1:57 ` Wei Fang
2026-01-21 8:37 ` [PATCH v2] net: fec: account for VLAN header in frame length calculations Clemens Gruber
2026-01-22 6:07 ` Wei Fang
2026-01-22 12:23 ` Paolo Abeni
2026-01-22 12: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=176908500535.1702959.10720487953177513534.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=mail@clemensgruber.at \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shenwei.wang@nxp.com \
--cc=stable@kernel.org \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.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