From: patchwork-bot+netdevbpf@kernel.org
To: Vivian Wang <wangruikang@iscas.ac.cn>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, dlan@gentoo.org,
vadim.fedorenko@linux.dev, maxime.chevallier@bootlin.com,
pjw@kernel.org, palmer@dabbelt.com, alex@ghiti.fr,
troy.mitchell@linux.spacemit.com, amadeus@jmu.edu.cn,
michael.opdenacker@rootcommit.com, netdev@vger.kernel.org,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3] net: spacemit: Check for netif_carrier_ok() in emac_stats_update()
Date: Tue, 27 Jan 2026 04:00:09 +0000 [thread overview]
Message-ID: <176948640910.677485.7954248952886250088.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260123-k1-ethernet-clarify-stat-timeout-v3-1-93b9df627e87@iscas.ac.cn>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 23 Jan 2026 11:52:23 +0800 you wrote:
> Some PHYs stop the refclk for power saving, usually while link down.
> This causes reading stats to time out.
>
> Therefore, in emac_stats_update(), also don't update and reschedule if
> !netif_carrier_ok(). But that means we could be missing later updates if
> the link comes back up, so also reschedule when link up is detected in
> emac_adjust_link().
>
> [...]
Here is the summary with links:
- [net,v3] net: spacemit: Check for netif_carrier_ok() in emac_stats_update()
https://git.kernel.org/netdev/net/c/2c84959167d6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-01-27 4:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 3:52 [PATCH net v3] net: spacemit: Check for netif_carrier_ok() in emac_stats_update() Vivian Wang
2026-01-27 4:00 ` patchwork-bot+netdevbpf [this message]
2026-01-27 11:02 ` [PATCH net v3] net: spacemit: Check for netif_carrier_ok() in emac_stats_update(): manual merge Matthieu Baerts
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=176948640910.677485.7954248952886250088.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alex@ghiti.fr \
--cc=amadeus@jmu.edu.cn \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dlan@gentoo.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maxime.chevallier@bootlin.com \
--cc=michael.opdenacker@rootcommit.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=troy.mitchell@linux.spacemit.com \
--cc=vadim.fedorenko@linux.dev \
--cc=wangruikang@iscas.ac.cn \
/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