Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH net-next] net: dsa: lantiq_gswip: enable jumbo frames on GSWIP
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <164697301321.12732.1511628765770626834.git-patchwork-notify@kernel.org>
Date:   Fri, 11 Mar 2022 04:30:13 +0000
References: <20220308230457.1599237-1-olek2@wp.pl>
In-Reply-To: <20220308230457.1599237-1-olek2@wp.pl>
To:     Aleksander Jan Bajkowski <olek2@wp.pl>
Cc:     hauke@hauke-m.de, andrew@lunn.ch, vivien.didelot@gmail.com,
        f.fainelli@gmail.com, olteanv@gmail.com, davem@davemloft.net,
        kuba@kernel.org, linux@armlinux.org.uk, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org, tom@tomn.co.uk
Precedence: bulk

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Wed,  9 Mar 2022 00:04:57 +0100 you wrote:
> This enables non-standard MTUs on a per-port basis, with the overall
> frame size set based on the CPU port.
> 
> When the MTU is not changed, this should have no effect.
> 
> Long packets crash the switch with MTUs of greater than 2526, so the
> maximum is limited for now. Medium packets are sometimes dropped (e.g.
> TCP over 2477, UDP over 2516-2519, ICMP over 2526), Hence an MTU value
> of 2400 seems safe.
> 
> [...]

Here is the summary with links:
  - [net-next] net: dsa: lantiq_gswip: enable jumbo frames on GSWIP
    https://git.kernel.org/netdev/net-next/c/c40bb4fedcd6

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html