From: Kyle Switch <kyle.switch@motor-comm.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Frank.Sae@motor-comm.com, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
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 v11] net: phy: Add driver for Motorcomm Quad 2.5GbE phy
Date: Thu, 20 Aug 2026 09:12:37 +0800 [thread overview]
Message-ID: <6327f6c2-65f8-45d6-b890-0f371ba8e36b@motor-comm.com> (raw)
In-Reply-To: <20260817083748.05f798ba@kernel.org>
On 8/17/26 23:37, Jakub Kicinski wrote:
> On Mon, 17 Aug 2026 19:06:26 +0800 Kyle Switch wrote:
>> Add support for Motorcomm YT8824 quad-port 2.5G PHY to the existing
>> motorcomm driver, using the phy_package helpers for the shared top
>> extended register space.
>> It also adds a new exported phylib helper,genphy_c45_template_testmode(),
>> plus two new definitions in the MDIO uAPI header.
> ## Form letter - net-next-closed
>
> The merge window for v7.3 has started, and therefore net-next is closed
> for new drivers, features, code refactoring and optimizations.
> We will only consider applying net-next patches which were posted
> before the announcement:
>
> https://lore.kernel.org/20260816155953.072d73da@kernel.org
>
> Fixes are obviously welcome at any time. net-next patches may be sent
> for review and discussion only with an RFC tag.
>
> Please repost when net-next reopens.
>
> See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
Ans: OK.
next prev parent reply other threads:[~2026-08-20 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 11:06 [PATCH net-next v11] net: phy: Add driver for Motorcomm Quad 2.5GbE phy Kyle Switch
2026-08-17 15:37 ` Jakub Kicinski
2026-08-20 1:12 ` Kyle Switch [this message]
2026-08-18 1:13 ` Andrew Lunn
2026-08-20 1:15 ` 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=6327f6c2-65f8-45d6-b890-0f371ba8e36b@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