From: patchwork-bot+netdevbpf@kernel.org
To: Jonas Gorski <jonas.gorski@gmail.com>
Cc: florian.fainelli@broadcom.com, andrew@lunn.ch, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, murali.policharla@broadcom.com,
linux@armlinux.org.uk, f.fainelli@gmail.com,
vladimir.oltean@nxp.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] net: dsa: b53: assorted jumbo frame fixes
Date: Tue, 08 Oct 2024 08:50:32 +0000 [thread overview]
Message-ID: <172837743273.451237.9546651713497729915.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241004-b53_jumbo_fixes-v1-0-ce1e54aa7b3c@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 04 Oct 2024 10:47:16 +0200 you wrote:
> While investigating the capabilities of BCM63XX's integrated switch and
> its DMA engine, I noticed a few issues in b53's jumbo frame code.
>
> Mostly a confusion of MTU vs frame length, but also a few missing cases
> for 100M switches.
>
> Tested on BCM63XX and BCM53115 with intel 1G and realtek 1G NICs,
> which support MTUs of 9000 or slightly above, but significantly less
> than the 9716/9720 supported by BCM53115, so I couldn't verify the
> actual maximum frame length.
>
> [...]
Here is the summary with links:
- [1/5] net: dsa: b53: fix jumbo frame mtu check
https://git.kernel.org/netdev/net/c/42fb3acf6826
- [2/5] net: dsa: b53: fix max MTU for 1g switches
https://git.kernel.org/netdev/net/c/680a8217dc00
- [3/5] net: dsa: b53: fix max MTU for BCM5325/BCM5365
https://git.kernel.org/netdev/net/c/ca8c1f71c101
- [4/5] net: dsa: b53: allow lower MTUs on BCM5325/5365
https://git.kernel.org/netdev/net/c/e4b294f88a32
- [5/5] net: dsa: b53: fix jumbo frames on 10/100 ports
https://git.kernel.org/netdev/net/c/2f3dcd0d39af
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-10-08 8:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 8:47 [PATCH 0/5] net: dsa: b53: assorted jumbo frame fixes Jonas Gorski
2024-10-04 8:47 ` [PATCH 1/5] net: dsa: b53: fix jumbo frame mtu check Jonas Gorski
2024-10-05 3:38 ` Florian Fainelli
2024-10-04 8:47 ` [PATCH 2/5] net: dsa: b53: fix max MTU for 1g switches Jonas Gorski
2024-10-05 3:38 ` Florian Fainelli
2024-10-04 8:47 ` [PATCH 3/5] net: dsa: b53: fix max MTU for BCM5325/BCM5365 Jonas Gorski
2024-10-05 3:39 ` Florian Fainelli
2024-10-04 8:47 ` [PATCH 4/5] net: dsa: b53: allow lower MTUs on BCM5325/5365 Jonas Gorski
2024-10-05 3:39 ` Florian Fainelli
2024-10-04 8:47 ` [PATCH 5/5] net: dsa: b53: fix jumbo frames on 10/100 ports Jonas Gorski
2024-10-05 3:40 ` Florian Fainelli
2024-10-08 8:50 ` 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=172837743273.451237.9546651713497729915.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=jonas.gorski@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=murali.policharla@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@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