From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: netdev-bot+sashiko@kernel.org, peilinhe2020@163.com
Cc: netdev@vger.kernel.org, alexandre.torgue@foss.st.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
he.peilin@zte.com.cn, jiang.kun2@zte.com.cn, kuba@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
mcoquelin.stm32@gmail.com, pabeni@redhat.com,
vbridgers2013@gmail.com, xu.xin16@zte.com.cn
Subject: Re: [PATCH net v7 1/2] net: stmmac: selftests: Prevent RXC from being disabled in LPI
Date: Thu, 17 Sep 2026 17:42:07 +0200 [thread overview]
Message-ID: <067b8ae8-7de4-47cb-bf49-ec6fde1f34d6@bootlin.com> (raw)
In-Reply-To: <178965769776.22033.13374439300724313005@kernel.org>
Hi
On 9/17/26 17:08, netdev-bot+sashiko@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential
> issue(s) to consider:
>
> Critical: 0 · High: 0 · Medium: 1 · Low: 0
>
> - [Medium] The last paragraph of the commit message describes the
> `eee_rx_clk_stop_enable` precondition backwards.
>
> --
>
> net: stmmac: selftests: Prevent RXC from being disabled in LPI
>
> The patch wraps the selftest loop in stmmac_selftest_run() with
> phylink_rx_clk_stop_block() / phylink_rx_clk_stop_unblock() so the PHY
> does not stop the receive clock while the MAC is in loopback. The code
> change itself looks balanced and is a no-op when the phylink config does
> not allow RX clock stop.
>
> The question below is only about the changelog, so the diff hunk is not
> quoted.
>
>> As the NETIF_F_VLAN_FEATURES may be empty on some platforms once the
>> software vlan stripping is removed, the phylink config attribute
>> 'eee_rx_clk_stop_enable' may no longer be inconditionnally set to
>> true, hence allowing RXC to be disabled during LPI on platforms
>> that don't have any VLAN features.
>
> [Severity: Medium]
> Is the true/false direction here inverted?
Yeah should say "eee_rx_clk_stop_enable' may no longer be unconditionnally
set to false", my bad...
Code is correct though.
>
> Related to that, should the changelog also mention that
> CONFIG_VLAN_8021Q=n builds are already affected today?
I'm fine with it.
Peilin He, are you ok with changing the commit log if you send another
iteration ?
Thanks for you work and for including this patch :)
Maxime
next prev parent reply other threads:[~2026-09-17 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 15:06 [PATCH net v7 0/2] net: stmmac: remove software VLAN tag stripping peilinhe2020
2026-09-14 15:06 ` [PATCH net v7 1/2] net: stmmac: selftests: Prevent RXC from being disabled in LPI peilinhe2020
2026-09-17 15:08 ` netdev-bot+sashiko
2026-09-17 15:42 ` Maxime Chevallier [this message]
2026-09-14 15:06 ` [PATCH net v7 2/2] net: stmmac: remove software VLAN tag stripping peilinhe2020
2026-09-17 15:08 ` netdev-bot+sashiko
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=067b8ae8-7de4-47cb-bf49-ec6fde1f34d6@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=he.peilin@zte.com.cn \
--cc=jiang.kun2@zte.com.cn \
--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=mcoquelin.stm32@gmail.com \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peilinhe2020@163.com \
--cc=vbridgers2013@gmail.com \
--cc=xu.xin16@zte.com.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
all inboxes | Powered by JetHome®