From: Gerhard Engleder <gerhard@engleder-embedded.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
imx@lists.linux.dev, linux-omap@vger.kernel.org,
Andrew Lunn <andrew@lunn.ch>, Andrew Lunn <andrew+netdev@lunn.ch>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
David Miller <davem@davemloft.net>, Wei Fang <wei.fang@nxp.com>,
Shenwei Wang <shenwei.wang@nxp.com>,
Clark Wang <xiaoning.wang@nxp.com>,
Siddharth Vadapalli <s-vadapalli@ti.com>,
Roger Quadros <rogerq@kernel.org>
Subject: Re: [PATCH net-next 2/4] net: fec: use new iterator phy_for_each
Date: Fri, 17 Oct 2025 22:51:29 +0200 [thread overview]
Message-ID: <9e96d5ce-ef8f-4200-bad7-09618cac8f28@engleder-embedded.com> (raw)
In-Reply-To: <fff4a855-d7d4-4543-a11b-e3e1f6611196@gmail.com>
On 17.10.25 22:41, Heiner Kallweit wrote:
> Use new iterator phy_for_each() to simplify the code.
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> ---
> drivers/net/ethernet/freescale/fec_main.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/ethernet/freescale/fec_main.c b/drivers/net/ethernet/freescale/fec_main.c
> index 1edcfaee6..d7c39ef2d 100644
> --- a/drivers/net/ethernet/freescale/fec_main.c
> +++ b/drivers/net/ethernet/freescale/fec_main.c
> @@ -2552,7 +2552,6 @@ static int fec_enet_mii_init(struct platform_device *pdev)
> int err = -ENXIO;
> u32 mii_speed, holdtime;
> u32 bus_freq;
> - int addr;
>
> /*
> * The i.MX28 dual fec interfaces are not equal.
> @@ -2667,11 +2666,8 @@ static int fec_enet_mii_init(struct platform_device *pdev)
> of_node_put(node);
>
> /* find all the PHY devices on the bus and set mac_managed_pm to true */
> - for (addr = 0; addr < PHY_MAX_ADDR; addr++) {
> - phydev = mdiobus_get_phy(fep->mii_bus, addr);
> - if (phydev)
> - phydev->mac_managed_pm = true;
> - }
> + phy_for_each(fep->mii_bus, phydev)
> + phydev->mac_managed_pm = true;
>
> mii_cnt++;
>
Reviewed-by: Gerhard Engleder <gerhard@engleder-embedded.com>
next prev parent reply other threads:[~2025-10-17 20:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 20:39 [PATCH net-next 0/4] net: phy: add iterator phy_for_each Heiner Kallweit
2025-10-17 20:41 ` [PATCH net-next 1/4] " Heiner Kallweit
2025-10-17 20:51 ` Gerhard Engleder
2025-10-22 1:24 ` Jakub Kicinski
2025-10-22 2:00 ` Andrew Lunn
2025-10-17 20:41 ` [PATCH net-next 2/4] net: fec: use new " Heiner Kallweit
2025-10-17 20:51 ` Gerhard Engleder [this message]
2025-10-17 20:42 ` [PATCH net-next 3/4] net: davinci_mdio: " Heiner Kallweit
2025-10-17 20:51 ` Gerhard Engleder
2025-10-17 20:43 ` [PATCH net-next 4/4] net: phy: use new iterator phy_for_each in mdiobus_prevent_c45_scan Heiner Kallweit
2025-10-17 20:52 ` Gerhard Engleder
2025-10-20 2:44 ` [PATCH net-next 0/4] net: phy: add iterator phy_for_each Wei Fang
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=9e96d5ce-ef8f-4200-bad7-09618cac8f28@engleder-embedded.com \
--to=gerhard@engleder-embedded.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rogerq@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=shenwei.wang@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