From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Sanju=C3=A1n_Garc=C3=ADa=2C_Jorge_=3CJorge=2ESanjuanGarcia=40duago?=@ci.codeaurora.org,
=?utf-8?q?n=2Ecom=3E?=@ci.codeaurora.org
Cc: andrew@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, s-vadapalli@ti.com,
grygorii.strashko@ti.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 0/1] net: ethernet: ti: am65-cpsw: Allow for MTU values
Date: Fri, 12 Jan 2024 01:00:28 +0000 [thread overview]
Message-ID: <170502122817.27071.16313545781021735290.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240105085530.14070-1-jorge.sanjuangarcia@duagon.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 5 Jan 2024 08:55:39 +0000 you wrote:
> The am65-cpsw-nuss driver has a fixed definition for the maximum ethernet
> frame length of 1522 bytes (AM65_CPSW_MAX_PACKET_SIZE). This limits the switch
> ports to only operate at a maximum MTU of 1500 bytes. When combining this CPSW
> switch with a DSA switch connected to one of its ports this limitation shows up.
> The extra 8 bytes the DSA subsystem adds internally to the ethernet frame
> create resulting frames bigger than 1522 bytes (1518 for non VLAN + 8 for DSA
> stuff) so they get dropped by the switch.
>
> [...]
Here is the summary with links:
- [net,v2,1/1] net: ethernet: ti: am65-cpsw: Fix max mtu to fit ethernet frames
https://git.kernel.org/netdev/net/c/64e47d8afb5c
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:[~2024-01-12 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 8:55 Sanjuán García, Jorge
2024-01-05 8:55 ` [PATCH net v2 1/1] net: ethernet: ti: am65-cpsw: Fix max mtu to fit ethernet frames Sanjuán García, Jorge
2024-01-11 9:18 ` Horatiu Vultur
2024-01-11 9:46 ` Siddharth Vadapalli
2024-01-12 1: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=170502122817.27071.16313545781021735290.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Sanju=C3=A1n_Garc=C3=ADa=2C_Jorge_=3CJorge=2ESanjuanGarcia=40duago?=@ci.codeaurora.org \
--cc==?utf-8?q?n=2Ecom=3E?=@ci.codeaurora.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=grygorii.strashko@ti.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=s-vadapalli@ti.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
all inboxes | Powered by JetHome®