From: patchwork-bot+netdevbpf@kernel.org
To: Corentin Labbe <clabbe@baylibre.com>
Cc: alexandre.torgue@st.com, davem@davemloft.net,
jernej.skrabec@siol.net, joabreu@synopsys.com,
marek.belisko@gmail.com, mripard@kernel.org,
peppe.cavallaro@st.com, wens@csie.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net: stmmac: dwmac-sun8i: Provide TX and RX fifo sizes
Date: Fri, 19 Mar 2021 20:50:08 +0000 [thread overview]
Message-ID: <161618700844.7421.17310950197436009326.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210319134422.9351-1-clabbe@baylibre.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Fri, 19 Mar 2021 13:44:22 +0000 you wrote:
> MTU cannot be changed on dwmac-sun8i. (ip link set eth0 mtu xxx returning EINVAL)
> This is due to tx_fifo_size being 0, since this value is used to compute valid
> MTU range.
> Like dwmac-sunxi (with commit 806fd188ce2a ("net: stmmac: dwmac-sunxi: Provide TX and RX fifo sizes"))
> dwmac-sun8i need to have tx and rx fifo sizes set.
> I have used values from datasheets.
> After this patch, setting a non-default MTU (like 1000) value works and network is still useable.
>
> [...]
Here is the summary with links:
- net: stmmac: dwmac-sun8i: Provide TX and RX fifo sizes
https://git.kernel.org/netdev/net/c/014dfa26ce1c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-03-19 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 13:44 [PATCH] net: stmmac: dwmac-sun8i: Provide TX and RX fifo sizes Corentin Labbe
2021-03-19 20: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=161618700844.7421.17310950197436009326.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=clabbe@baylibre.com \
--cc=davem@davemloft.net \
--cc=jernej.skrabec@siol.net \
--cc=joabreu@synopsys.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.belisko@gmail.com \
--cc=mripard@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=wens@csie.org \
/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;
as well as URLs for NNTP newsgroup(s).