From: Andrew Lunn <andrew@lunn.ch>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: hkallweit1@gmail.com, linux@armlinux.org.uk, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
richardcochran@gmail.com, o.rempel@pengutronix.de,
alok.a.tiwari@oracle.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v5 1/4] net: phy: micrel: Start using PHY_ID_MATCH_MODEL
Date: Wed, 20 Aug 2025 05:14:48 +0200 [thread overview]
Message-ID: <585233b2-0462-4815-bdcc-b91460e1cac5@lunn.ch> (raw)
In-Reply-To: <20250818075121.1298170-2-horatiu.vultur@microchip.com>
On Mon, Aug 18, 2025 at 09:51:18AM +0200, Horatiu Vultur wrote:
> Start using PHY_ID_MATCH_MODEL for all the drivers.
> While at this add also PHY_ID_KSZ8041RNLI to micrel_tbl.
>
> It is safe to change the current of 0x00fffff0 to PHY_ID_MATCH_MODEL
> because all the micrel PHYs have in MSB a value of 0.
>
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2025-08-20 3:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 7:51 [PATCH net-next v5 0/4] net: phy: micrel: Add support for lan8842 Horatiu Vultur
2025-08-18 7:51 ` [PATCH net-next v5 1/4] net: phy: micrel: Start using PHY_ID_MATCH_MODEL Horatiu Vultur
2025-08-20 3:14 ` Andrew Lunn [this message]
2025-08-18 7:51 ` [PATCH net-next v5 2/4] net: phy: micrel: Introduce lanphy_modify_page_reg Horatiu Vultur
2025-08-18 7:51 ` [PATCH net-next v5 3/4] net: phy: micrel: Replace hardcoded pages with defines Horatiu Vultur
2025-08-18 7:51 ` [PATCH net-next v5 4/4] net: phy: micrel: Add support for lan8842 Horatiu Vultur
2025-08-20 3:18 ` Andrew Lunn
2025-08-21 8:50 ` [PATCH net-next v5 0/4] " patchwork-bot+netdevbpf
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=585233b2-0462-4815-bdcc-b91460e1cac5@lunn.ch \
--to=andrew@lunn.ch \
--cc=alok.a.tiwari@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.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
all inboxes | Powered by JetHome®