From: Paolo Abeni <pabeni@redhat.com>
To: Kyle Switch <kyle.switch@motor-comm.com>,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, andrew@lunn.ch, 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
Cc: 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 0/3] net: phy: Add driver for Motorcomm Quad 2.5GbE phy
Date: Tue, 22 Sep 2026 12:23:27 +0200 [thread overview]
Message-ID: <a5fa376d-0826-4fdc-b99e-cc4a0a623cbc@redhat.com> (raw)
In-Reply-To: <20260917131441.3428554-1-kyle.switch@motor-comm.com>
On 9/17/26 15:14, Kyle Switch wrote:
> changes in v20:
> patch 1: Add phy-mode description in properties in
> motorcomm,yt8824.yaml
At least some of the sashiko comments looks legit and
relevant to me.
Note that the cover letter must carry some brief relevant
description of the overall work.
/P
next prev parent reply other threads:[~2026-09-22 10:23 UTC|newest]
Thread overview: 13+ 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-18 13:15 ` sashiko-bot
2026-09-21 13:17 ` netdev-bot+sashiko
2026-09-22 12:10 ` Andrew Lunn
2026-09-23 1:00 ` Kyle Switch
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-18 13:15 ` sashiko-bot
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 ` Paolo Abeni [this message]
2026-09-23 1:05 ` [PATCH net-next v20 0/3] " 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=a5fa376d-0826-4fdc-b99e-cc4a0a623cbc@redhat.com \
--to=pabeni@redhat.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=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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.