From: Chukun Pan <amadeus@jmu.edu.cn>
To: javen_xu@realsil.com.cn
Cc: amadeus@jmu.edu.cn, andrew@lunn.ch, daniel@makrotopia.org,
davem@davemloft.net, edumazet@google.com,
freddy_gu@realsil.com.cn, hkallweit1@gmail.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
maxime.chevallier@bootlin.com, nb@tipi-net.de,
netdev@vger.kernel.org, pabeni@redhat.com,
vladimir.oltean@nxp.com
Subject: Re: [PATCH net-next v10 5/5] net: phy: realtek: add support for RTL8261D
Date: Tue, 28 Jul 2026 14:50:01 +0800 [thread overview]
Message-ID: <20260728065001.1487282-1-amadeus@jmu.edu.cn> (raw)
In-Reply-To: <bb782164800a421397c2085f7e58aff4@realsil.com.cn>
Hi,
> The reason for this change is that RTL8261 10Gbps PHY share the same
> phy id. The specific hardware versions are distinguished by a sub-phy
> id instead. And in probe function, we will print out the exact hardware
> version explicitly.
This is only printed during probe. If I'm not mistaken, the PHY IDs
of RTL8261N and RTL8261C are not the same. Perhaps you could name it
something like RTL8261C/D here?
next prev parent reply other threads:[~2026-07-28 6:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 2:24 [PATCH net-next v10 0/5] Add support for RTL8261 javen
2026-07-21 2:24 ` [PATCH net-next v10 1/5] net: phy: c45: add genphy_c45_pma_soft_reset() javen
2026-07-21 6:52 ` Maxime Chevallier
2026-07-21 2:24 ` [PATCH net-next v10 2/5] net: phy: c45: add setup and read master/slave helpers javen
2026-07-21 2:24 ` [PATCH net-next v10 3/5] net: phy: realtek: add support for RTL8261C_CG javen
2026-07-21 2:24 ` [PATCH net-next v10 4/5] net: phy: realtek: load firmware " javen
2026-07-21 2:24 ` [PATCH net-next v10 5/5] net: phy: realtek: add support for RTL8261D javen
2026-07-21 6:57 ` Maxime Chevallier
2026-07-22 12:18 ` Chukun Pan
[not found] ` <202607270134.66R1YOaT41072024@rtits1.realtek.com.tw>
2026-07-27 1:45 ` Javen
2026-07-28 6:50 ` Chukun Pan [this message]
2026-07-28 7:30 ` Javen
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=20260728065001.1487282-1-amadeus@jmu.edu.cn \
--to=amadeus@jmu.edu.cn \
--cc=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=freddy_gu@realsil.com.cn \
--cc=hkallweit1@gmail.com \
--cc=javen_xu@realsil.com.cn \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@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