Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: andrew+netdev@lunn.ch, kuba@kernel.org, davem@davemloft.net,
	edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
	mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
	linux@armlinux.org.uk, thomas.petazzoni@bootlin.com,
	alexis.lothore@bootlin.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH net-next 0/2] net: stmmac: Cleanup rx coalescing computation when using RIWT
Date: Tue, 04 Aug 2026 01:50:14 +0000	[thread overview]
Message-ID: <178580821438.2913307.10017683576948175054.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260802114015.214212-1-maxime.chevallier@bootlin.com>

Hello:

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

On Sun,  2 Aug 2026 13:40:12 +0200 you wrote:
> Currently when configuring interrupt coalescing on devices that relies
> on the Receive Interrupt Watchdog Timer feature of dwmac, the
> computation of the RIWT timings leads to off-by-one values when
> reporting the timings back to userspace.
> 
> RIWT works by arming a watchdog timer upon receiving frames with the RI
> bit not set in the descriptor. The timer duration is expressed in units
> of 256 stmmac clock ticks, and therefore requires a bit of computation
> to derive it :
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] net: stmmac: ethtool: Comment the magic numbers in RIWT computation
    https://git.kernel.org/netdev/net-next/c/b6a89c8ef34f
  - [net-next,2/2] net: stmmac: ethtool: Address off-by-one when reading the coal rx-usecs
    https://git.kernel.org/netdev/net-next/c/ae88f78bc4eb

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-08-04  1:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-02 11:40 [PATCH net-next 0/2] net: stmmac: Cleanup rx coalescing computation when using RIWT Maxime Chevallier
2026-08-02 11:40 ` [PATCH net-next 1/2] net: stmmac: ethtool: Comment the magic numbers in RIWT computation Maxime Chevallier
2026-08-02 15:02   ` Andrew Lunn
2026-08-02 11:40 ` [PATCH net-next 2/2] net: stmmac: ethtool: Address off-by-one when reading the coal rx-usecs Maxime Chevallier
2026-08-02 15:05   ` Andrew Lunn
2026-08-02 20:29     ` Maxime Chevallier
2026-08-02 23:16       ` Andrew Lunn
2026-08-04  1: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=178580821438.2913307.10017683576948175054.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=alexis.lothore@bootlin.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@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=linux@armlinux.org.uk \
    --cc=maxime.chevallier@bootlin.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=thomas.petazzoni@bootlin.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