From: Jakub Kicinski <kuba@kernel.org>
To: "Frank.sae" <frank.sae@motor-comm.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
pabeni@redhat.com, edumazet@kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lingyu.zou@motor-comm.com, xiaoyong.li@motor-comm.com,
jie.han@motor-comm.com
Subject: Re: [PATCH net-next v?] [PATCH net-next] net: phy: motorcomm: add YT8831 2.5G PHY support
Date: Mon, 26 Oct 2026 17:17:00 -0700 [thread overview]
Message-ID: <20261026171700.06ce6543@kernel.org> (raw)
In-Reply-To: <20261022054642.1332801-1-frank.sae@motor-comm.com>
On Thu, 22 Oct 2026 05:46:42 +0000 Frank.sae wrote:
> Add a driver for motorcomm yt8831/yt8821-vd ethernet phy.
> Verified the driver in BPI-R3(with MTK Filogic-830 Soc)development board
> YT8831 works in AUTO_BX2500_SGMII or FORCE_BX2500 interface,
> supports 2.5G/1000M/100M/10M speeds, and wol(magic package)
## Form letter - net-next-closed
The merge window for Linux v7.4 has begun, and the net-next
tree is now closed for new drivers, features, code refactoring
and optimizations. We are currently accepting bug fixes only.
Please repost when net-next reopens. There is some uncertainty
about how long this merge window will last, so please check
https://netdev.bots.linux.dev/net-next.html
before reposting. net-next _may_ reopen on Nov 2nd.
See:
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
> +/**
> + * yt8831_set_wol() - turn wake-on-lan on or off
> + * @phydev: a pointer to a &struct phy_device
> + * @wol: a pointer to a &struct ethtool_wolinfo
> + *
> + * NOTE: YT8831_WOL_CONFIG_REG is common ext reg.
> + */
> +static int yt8831_set_wol(struct phy_device *phydev,
> + struct ethtool_wolinfo *wol)
Please run scripts/kernel-doc -Wall on this, the return
value must be documented in newly added kdoc.
--
pw-bot: defer
pv-bot: closed
prev parent reply other threads:[~2026-10-27 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 5:46 Frank.sae
2026-10-27 0:17 ` Jakub Kicinski [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=20261026171700.06ce6543@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=frank.sae@motor-comm.com \
--cc=hkallweit1@gmail.com \
--cc=jie.han@motor-comm.com \
--cc=lingyu.zou@motor-comm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xiaoyong.li@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®