From: Andrew Lunn <andrew@lunn.ch>
To: Harini Katakam <harini.katakam@amd.com>
Cc: hkallweit1@gmail.com, linux@armlinux.org.uk, davem@davemloft.net,
kuba@kernel.org, edumazet@google.com, pabeni@redhat.com,
vladimir.oltean@nxp.com, wsa+renesas@sang-engineering.com,
simon.horman@corigine.com, mkl@pengutronix.de,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
harinikatakamlinux@gmail.com, michal.simek@amd.com,
radhey.shyam.pandey@amd.com
Subject: Re: [PATCH net-next v3 1/3] phy: mscc: Use PHY_ID_MATCH_VENDOR to minimize PHY ID table
Date: Thu, 11 May 2023 16:05:41 +0200 [thread overview]
Message-ID: <428db3e5-fb22-45a3-8d75-85cfbf67fe56@lunn.ch> (raw)
In-Reply-To: <20230511120808.28646-2-harini.katakam@amd.com>
On Thu, May 11, 2023 at 05:38:06PM +0530, Harini Katakam wrote:
> All the PHY devices variants specified have the same mask and
> hence can be simplified to one vendor look up for 0x00070400.
> Any individual config can be identified by PHY_ID_MATCH_EXACT
> in the respective structure.
>
> Signed-off-by: Harini Katakam <harini.katakam@amd.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2023-05-11 14:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 12:08 [PATCH net-next v3 0/3] Add support for VSC8531_02 PHY and DT RGMII tuning Harini Katakam
2023-05-11 12:08 ` [PATCH net-next v3 1/3] phy: mscc: Use PHY_ID_MATCH_VENDOR to minimize PHY ID table Harini Katakam
2023-05-11 14:05 ` Andrew Lunn [this message]
2023-05-11 12:08 ` [PATCH net-next v3 2/3] phy: mscc: Add support for RGMII delay configuration Harini Katakam
2023-05-11 14:00 ` Simon Horman
2023-05-13 18:23 ` kernel test robot
2023-05-11 12:08 ` [PATCH net-next v3 3/3] phy: mscc: Add support for VSC8531_02 Harini Katakam
2023-05-11 14:11 ` Andrew Lunn
2023-05-11 16:17 ` Katakam, Harini
2023-05-11 14:16 ` Andrew Lunn
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=428db3e5-fb22-45a3-8d75-85cfbf67fe56@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=harini.katakam@amd.com \
--cc=harinikatakamlinux@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michal.simek@amd.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radhey.shyam.pandey@amd.com \
--cc=simon.horman@corigine.com \
--cc=vladimir.oltean@nxp.com \
--cc=wsa+renesas@sang-engineering.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®