From: patchwork-bot+netdevbpf@kernel.org
To: David Thompson <davthompson@nvidia.com>
Cc: bryan.whitehead@microchip.com, UNGLinuxDriver@microchip.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net: lan743x: permit VLAN-tagged packets up to configured MTU
Date: Tue, 02 Jun 2026 21:20:05 +0000 [thread overview]
Message-ID: <178043520515.1054744.8222539332561002723.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260529210300.433135-1-davthompson@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 29 May 2026 21:03:00 +0000 you wrote:
> VLAN-tagged interfaces on lan743x devices were previously unreachable via
> SSH and failed to respond to large ping packets (e.g. "ping -s 1469" given
> MTU=1500). In these scenarios, "ethtool -S" reports non-zero "RX Oversize
> Frame Errors". According to Microchip AN2948, the MAC_RX FSE (VLAN field
> size enforcement) bit determines whether frames with VLAN tags exceeding
> the base MTU plus tag length are discarded.
>
> [...]
Here is the summary with links:
- [net,v2] net: lan743x: permit VLAN-tagged packets up to configured MTU
https://git.kernel.org/netdev/net/c/8173d22b211f
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-06-02 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 21:03 David Thompson
2026-06-01 3:33 ` Thangaraj.S
2026-06-01 7:58 ` Nicolai Buchwitz
2026-06-02 21:20 ` 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=178043520515.1054744.8222539332561002723.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=bryan.whitehead@microchip.com \
--cc=davem@davemloft.net \
--cc=davthompson@nvidia.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome