From: Kyle Switch <kyle.switch@motor-comm.com>
To: Andrew Lunn <andrew@lunn.ch>, netdev-bot+sashiko@kernel.org
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, hkallweit1@gmail.com,
linux@armlinux.org.uk, Frank.Sae@motor-comm.com,
netdev@vger.kernel.org, devicetree@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 v20 1/3] dt-bindings: net: Document Motorcomm YT8824 PHY package
Date: Wed, 23 Sep 2026 09:00:26 +0800 [thread overview]
Message-ID: <c4c3476f-5e28-4ee4-a65e-e23806e7c13c@motor-comm.com> (raw)
In-Reply-To: <26e31b64-98bf-45d8-8c9b-b7291a3d783c@lunn.ch>
On 9/22/26 20:10, Andrew Lunn wrote:
>> MOTORCOMM PHY DRIVER
>> M: Frank <Frank.Sae@motor-comm.com>
>> L: netdev@vger.kernel.org
>> S: Maintained
>> F: Documentation/devicetree/bindings/net/motorcomm,yt8xxx.yaml
>> F: drivers/net/phy/motorcomm.c
>>
>> That pattern does not match motorcomm,yt8824.yaml, and no other section
>> matches it either, so get_maintainer.pl will not report the Motorcomm PHY
>> maintainer for future changes to this file. Widening the existing entry to
>> Documentation/devicetree/bindings/net/motorcomm,yt8*.yaml, or adding a new
>> F: line, would cover it.
> Please do fix this.
Ans: okay, Another question I'd like to ask is whether all the risk issues
flagged by sashiko need to be resolved. Some of the flags may not actually
be bugs, and some that are clearly meaningful have been fixed
one after another previously, so what I want to know is whether everything
flagged by sashiko has to be cleared. Thank you.
>
> Andrew
next prev parent reply other threads:[~2026-09-23 1:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 13:14 [PATCH net-next v20 0/3] net: phy: Add driver for Motorcomm Quad 2.5GbE phy Kyle Switch
2026-09-17 13:14 ` [PATCH net-next v20 1/3] dt-bindings: net: Document Motorcomm YT8824 PHY package Kyle Switch
2026-09-21 13:17 ` netdev-bot+sashiko
2026-09-22 12:10 ` Andrew Lunn
2026-09-23 1:00 ` Kyle Switch [this message]
2026-09-17 13:14 ` [PATCH net-next v20 2/3] net: phy: Add support for Template Control register for PMA Kyle Switch
2026-09-21 13:17 ` netdev-bot+sashiko
2026-09-17 13:14 ` [PATCH net-next v20 3/3] net: phy: Add driver for Motorcomm Quad 2.5GbE phy Kyle Switch
2026-09-21 13:17 ` netdev-bot+sashiko
2026-09-22 10:23 ` [PATCH net-next v20 0/3] " Paolo Abeni
2026-09-23 1:05 ` 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=c4c3476f-5e28-4ee4-a65e-e23806e7c13c@motor-comm.com \
--to=kyle.switch@motor-comm.com \
--cc=Frank.Sae@motor-comm.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=jianmin.wang@motor-comm.com \
--cc=jie.han@motor-comm.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ming.xu@motor-comm.com \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--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
all inboxes | Powered by JetHome®