From: Andrew Lunn <andrew@lunn.ch>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Marek Vasut <marex@denx.de>, Wei Fang <wei.fang@nxp.com>,
Clark Wang <xiaoning.wang@nxp.com>
Subject: Re: [PATCH net-next 2/3] net: phy: realtek: eliminate has_phycr2 variable
Date: Thu, 6 Nov 2025 14:52:06 +0100 [thread overview]
Message-ID: <ea476549-14e1-4208-8b5c-6659eafda988@lunn.ch> (raw)
In-Reply-To: <20251106111003.37023-3-vladimir.oltean@nxp.com>
On Thu, Nov 06, 2025 at 01:10:02PM +0200, Vladimir Oltean wrote:
> This variable is assigned in rtl821x_probe() and used in
> rtl8211f_config_init(), which is more complex than it needs to be.
> Simply testing the same condition from rtl821x_probe() in
> rtl8211f_config_init() yields the same result (the PHY driver ID is a
> runtime invariant), but with one temporary variable less.
>
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2025-11-06 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 11:10 [PATCH net-next 0/3] Disable CLKOUT on RTL8211F(D)(I)-VD-CG Vladimir Oltean
2025-11-06 11:10 ` [PATCH net-next 1/3] net: phy: realtek: eliminate priv->phycr2 variable Vladimir Oltean
2025-11-06 13:51 ` Andrew Lunn
2025-11-06 14:47 ` Vladimir Oltean
2025-11-06 11:10 ` [PATCH net-next 2/3] net: phy: realtek: eliminate has_phycr2 variable Vladimir Oltean
2025-11-06 13:52 ` Andrew Lunn [this message]
2025-11-06 11:10 ` [PATCH net-next 3/3] net: phy: realtek: allow CLKOUT to be disabled on RTL8211F(D)(I)-VD-CG Vladimir Oltean
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=ea476549-14e1-4208-8b5c-6659eafda988@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marex@denx.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@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