From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Wei Fang <wei.fang@nxp.com>, Shenwei Wang <shenwei.wang@nxp.com>,
"Clark Wang" <xiaoning.wang@nxp.com>,
Roger Quadros <rogerq@kernel.org>,
"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>,
Siddharth Vadapalli <s-vadapalli@ti.com>
Subject: Re: [PATCH v2 net-next 3/4] net: davinci_mdio: use new iterator mdiobus_for_each_phy
Date: Sat, 25 Oct 2025 10:57:19 +0530 [thread overview]
Message-ID: <7151c443585fc1c68327385582cd2dbca620a810.camel@ti.com> (raw)
In-Reply-To: <aadd3bd7-5cc5-45f5-b14d-d0b63629d612@gmail.com>
On Fri, 2025-10-24 at 22:23 +0200, Heiner Kallweit wrote:
> Use new iterator mdiobus_for_each_phy() to simplify the code.
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
Reviewed-by: Siddharth Vadapalli <s-vadapalli@ti.com>
Regards,
Siddharth.
next prev parent reply other threads:[~2025-10-25 5:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 20:20 [PATCH v2 net-next 0/4] net: phy: add iterator mdiobus_for_each_phy Heiner Kallweit
2025-10-24 20:21 ` [PATCH v2 net-next 1/4] " Heiner Kallweit
2025-10-24 20:22 ` [PATCH v2 net-next 2/4] net: fec: use new " Heiner Kallweit
2025-10-24 20:23 ` [PATCH v2 net-next 3/4] net: davinci_mdio: " Heiner Kallweit
2025-10-25 5:27 ` Siddharth Vadapalli [this message]
2025-10-24 20:24 ` [PATCH v2 net-next 4/4] net: phy: use new iterator mdiobus_for_each_phy in mdiobus_prevent_c45_scan Heiner Kallweit
2025-10-25 18:43 ` [PATCH v2 net-next 0/4] net: phy: add iterator mdiobus_for_each_phy Heiner Kallweit
2025-10-25 18:44 ` Heiner Kallweit
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=7151c443585fc1c68327385582cd2dbca620a810.camel@ti.com \
--to=s-vadapalli@ti.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=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;
as well as URLs for NNTP newsgroup(s).