From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kyle Switch <kyle.switch@motor-comm.com>,
Frank.Sae@motor-comm.com, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Cc: 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: Fri, 17 Jul 2026 22:19:39 +0200 [thread overview]
Message-ID: <6264d655-640e-47ec-9521-5e292bfeaba6@kernel.org> (raw)
In-Reply-To: <20260717054807.1321374-1-kyle.switch@motor-comm.com>
On 17/07/2026 07:48, 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>
Please run scripts/checkpatch.pl on the patches and fix reported
warnings. After that, run also 'scripts/checkpatch.pl --strict' on the
patches and (probably) fix more warnings. Some warnings can be ignored,
especially from --strict run, but the code here looks like it needs a
fix. Feel free to get in touch if the warning is not clear.
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC (and consider --no-git-fallback argument, so you will
not CC people just because they made one commit years ago). It might
happen, that command when run on an older kernel, gives you outdated
entries. Therefore please be sure you base your patches on recent Linux
kernel.
Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.
> ---
>
> 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 +
> drivers/net/phy/motorcomm.c | 1808 ++++++++++++++++-
> 2 files changed, 1750 insertions(+), 88 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/net/motorcomm,yt8xxx.yaml b/Documentation/devicetree/bindings/net/motorcomm,yt8xxx.yaml
> index 26688e2302ea..e7592468f658 100644
> --- a/Documentation/devicetree/bindings/net/motorcomm,yt8xxx.yaml
> +++ b/Documentation/devicetree/bindings/net/motorcomm,yt8xxx.yaml
> @@ -149,3 +149,33 @@ examples:
> motorcomm,auto-sleep-disabled;
> };
> };
> + - |
> + mdio {
> + #address-cells = <1>;
> + #size-cells = <0>;
I don't understand why you are doing this. Anyway, please read the
documents I linked and maybe there is some explanation for that change.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-07-17 20:19 UTC|newest]
Thread overview: 4+ 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-17 15:11 ` Andrew Lunn
2026-07-17 20:19 ` Krzysztof Kozlowski [this message]
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=6264d655-640e-47ec-9521-5e292bfeaba6@kernel.org \
--to=krzk@kernel.org \
--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=kyle.switch@motor-comm.com \
--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