All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Pengfei Zhang <zhangfeionline@gmail.com>
Cc: maxime.chevallier@bootlin.com, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
	pabeni@redhat.com, mcoquelin.stm32@gmail.com,
	alexandre.torgue@foss.st.com, Jose.Abreu@synopsys.com,
	zhangpengfei16@xiaomi.com, netdev@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: stmmac: fix RX coalesce frames counter
Date: Fri, 16 Oct 2026 00:10:10 +0000	[thread overview]
Message-ID: <179210941077.4168191.1895696190084335171.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261009111138.320089-1-zhangfeionline@gmail.com>

Hello:

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

On Fri,  9 Oct 2026 19:11:37 +0800 you wrote:
> The RX refill path should set the IC bit once every rx_coal_frames
> descriptors and leave the rest to the RX watchdog (RIWT), as done by
> commit d429b66e2ebc ("net: stmmac: Implement RX Coalesce Frames
> setting").
> 
> Since commit 6fa9d691b91a ("net: stmmac: Prevent divide-by-zero") the
> counter is increased by N+1 for each descriptor and then compared
> against N, so it is always reset to 0. With a non-zero rx-frames, IC is
> therefore set on every descriptor and every frame raises an interrupt.
> 
> [...]

Here is the summary with links:
  - [net] net: stmmac: fix RX coalesce frames counter
    https://git.kernel.org/netdev/net-next/c/0d20963e0aeb

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



      parent reply	other threads:[~2026-10-16  0:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 11:11 [PATCH net] net: stmmac: fix RX coalesce frames counter Pengfei Zhang
2026-10-09 11:14 ` netdev-bot+sinfo
2026-10-13  6:09   ` Pengfei Zhang
2026-10-16  0:10 ` 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=179210941077.4168191.1895696190084335171.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Jose.Abreu@synopsys.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=zhangfeionline@gmail.com \
    --cc=zhangpengfei16@xiaomi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.