From: Kyle Switch <kyle.switch@motor-comm.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Frank.Sae@motor-comm.com, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, ming.xu@motor-comm.com,
xiaolin.xu@motor-comm.com, jianmin.wang@motor-comm.com,
jie.han@motor-comm.com
Subject: Re: [Patch net-next v3] net: phy: Add driver for Motorcomm Quad 2.5GbE phy
Date: Mon, 20 Jul 2026 16:47:30 +0800 [thread overview]
Message-ID: <9ebac788-4ce9-4beb-9e98-4117abbd55ff@motor-comm.com> (raw)
In-Reply-To: <3a576b50-f2be-476f-b702-964a8158cf1a@lunn.ch>
On 7/17/26 22:53, Andrew Lunn wrote:
> On Fri, Jul 17, 2026 at 01:48:07PM +0800, Kyle Switch wrote:
>> Add a driver for motorcomm yt8824 quad 2.5G ethernet phy, supports
>> 2.5G/1000M/100M/10M speed.
>>
>> Signed-off-by: Kyle Switch <kyle.switch@motor-comm.com>
>> ---
>>
>> changes in v3:
>> 1. Using common apis defined in phy_package.c to handle shared top
>> extend register space.
>> 2. Add dts demo in motorcomm,yt8xxx.yaml.
>> 3. Fix unnecessary redundant judgments.
>> 4. Fix BMCR registers operation using magic number.
>> 5. Rename funtion based on its approximate functionality.
>>
>> changes in v2:
>> 1. Remove duplicate code and replace it with existing api.
>>
>> .../bindings/net/motorcomm,yt8xxx.yaml | 30 +
>
> Please put binding changes in a patch of its own, in the patch
> series. You also need to Cc: the DT people.
>
> Andrew
>
Ans: as mentioned in other emails. patch v4 will remove binding changes,
and updated in another patch thread.
> ---
> pw-bot: cr
next prev parent reply other threads:[~2026-07-20 8:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 5:48 [Patch net-next v3] net: phy: Add driver for Motorcomm Quad 2.5GbE phy Kyle Switch
2026-07-17 14:53 ` Andrew Lunn
2026-07-20 8:47 ` Kyle Switch [this message]
2026-07-17 15:11 ` Andrew Lunn
2026-07-20 9:05 ` Kyle Switch
2026-07-20 13:37 ` Andrew Lunn
2026-07-21 11:45 ` Kyle Switch
2026-07-17 20:19 ` Krzysztof Kozlowski
2026-07-20 8:45 ` Kyle Switch
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=9ebac788-4ce9-4beb-9e98-4117abbd55ff@motor-comm.com \
--to=kyle.switch@motor-comm.com \
--cc=Frank.Sae@motor-comm.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=jianmin.wang@motor-comm.com \
--cc=jie.han@motor-comm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ming.xu@motor-comm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xiaolin.xu@motor-comm.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