From: patchwork-bot+netdevbpf@kernel.org
To: Xiaoliang Yang <xiaoliang.yang_1@nxp.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kuba@kernel.org,
qiangqing.zhang@nxp.com, peppe.cavallaro@st.com,
alexandre.torgue@foss.st.com, joabreu@synopsys.com,
yannick.vignon@nxp.com, boon.leong.ong@intel.com,
Jose.Abreu@synopsys.com, mst@redhat.com, sonic.zhang@analog.com,
Joao.Pinto@synopsys.com, mingkai.hu@nxp.com, leoyang.li@nxp.com
Subject: Re: [PATCH net-next] net: stmmac: bump tc when get underflow error from DMA descriptor
Date: Mon, 13 Dec 2021 12:30:09 +0000 [thread overview]
Message-ID: <163939860926.21128.12756625004904393893.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211208100651.19369-1-xiaoliang.yang_1@nxp.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 8 Dec 2021 18:06:51 +0800 you wrote:
> In DMA threshold mode, frame underflow errors may sometimes occur when
> the TC(threshold control) value is not enough. The TC value need to be
> bumped up in this case.
>
> There is no underflow interrupt bit on DMA_CH(#i)_Status of dwmac4, so
> the DMA threshold cannot be bumped up in stmmac_dma_interrupt(). The
> i.mx8mp board observed an underflow error while running NFS boot, the
> NFS rootfs could not be mounted.
>
> [...]
Here is the summary with links:
- [net-next] net: stmmac: bump tc when get underflow error from DMA descriptor
https://git.kernel.org/netdev/net-next/c/3a6c12a0c6c3
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:[~2021-12-13 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 10:06 Xiaoliang Yang
2021-12-09 1:31 ` Joakim Zhang
2021-12-10 2:41 ` Jakub Kicinski
2021-12-10 3:11 ` [EXT] " Xiaoliang Yang
2021-12-10 16:06 ` Jakub Kicinski
2021-12-13 0:49 ` Xiaoliang Yang
2021-12-13 12:30 ` 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=163939860926.21128.12756625004904393893.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Joao.Pinto@synopsys.com \
--cc=Jose.Abreu@synopsys.com \
--cc=alexandre.torgue@foss.st.com \
--cc=boon.leong.ong@intel.com \
--cc=davem@davemloft.net \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingkai.hu@nxp.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=qiangqing.zhang@nxp.com \
--cc=sonic.zhang@analog.com \
--cc=xiaoliang.yang_1@nxp.com \
--cc=yannick.vignon@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
all inboxes | Powered by JetHome®