Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH net-next] net: stmmac: Set FIFO sizes for ipq806x
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <161568780813.10930.14410536335791157714.git-patchwork-notify@kernel.org>
Date:   Sun, 14 Mar 2021 02:10:08 +0000
References: <20210313131826.GA17553@earth.li>
In-Reply-To: <20210313131826.GA17553@earth.li>
To:     Jonathan McDowell <noodles@earth.li>
Cc:     peppe.cavallaro@st.com, alexandre.torgue@st.com,
        joabreu@synopsys.com, davem@davemloft.net, kuba@kernel.org,
        mcoquelin.stm32@gmail.com, netdev@vger.kernel.org,
        linux-stm32@st-md-mailman.stormreply.com,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Sat, 13 Mar 2021 13:18:26 +0000 you wrote:
> Commit eaf4fac47807 ("net: stmmac: Do not accept invalid MTU values")
> started using the TX FIFO size to verify what counts as a valid MTU
> request for the stmmac driver.  This is unset for the ipq806x variant.
> Looking at older patches for this it seems the RX + TXs buffers can be
> up to 8k, so set appropriately.
> 
> (I sent this as an RFC patch in June last year, but received no replies.
> I've been running with this on my hardware (a MikroTik RB3011) since
> then with larger MTUs to support both the internal qca8k switch and
> VLANs with no problems. Without the patch it's impossible to set the
> larger MTU required to support this.)
> 
> [...]

Here is the summary with links:
  - [net-next] net: stmmac: Set FIFO sizes for ipq806x
    https://git.kernel.org/netdev/net-next/c/e127906b68b4

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