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,
davem@davemloft.net, edumazet@kernel.org, pabeni@redhat.com,
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 v2] net: phy: motorcomm: add YT8831 2.5G PHY support
Date: Sun, 15 Nov 2026 11:05:38 -0800 [thread overview]
Message-ID: <20261115110538.20b35287@kernel.org> (raw)
In-Reply-To: <20261109064332.3381180-1-frank.sae@motor-comm.com>
On Mon, 9 Nov 2026 06:43:32 +0000 Frank.sae wrote:
> +/**
> + * yt8831_read_page() - read reg page
> + * @phydev: a pointer to a &struct phy_device
> + *
> + * returns current reg space of yt8831 (YT8831_RSSR_FIBER_SAPCE/
> + * YT8831_RSSR_UTP_SAPCE) or negative errno code
> + */
> +static int yt8831_read_page(struct phy_device *phydev)
You need to format the return statement correctly, kdoc requires
the following format:
* Returns: current tag..
this patch triggers:
Warning: drivers/net/phy/motorcomm.c:803 No description found for return value of 'yt8831_set_wol'
Warning: drivers/net/phy/motorcomm.c:964 No description found for return value of 'yt8831_read_page'
Warning: drivers/net/phy/motorcomm.c:1005 No description found for return value of 'yt8831_write_page'
Warning: drivers/net/phy/motorcomm.c:803 No description found for return value of 'yt8831_set_wol'
Warning: drivers/net/phy/motorcomm.c:964 No description found for return value of 'yt8831_read_page'
Warning: drivers/net/phy/motorcomm.c:1005 No description found for return value of 'yt8831_write_page'
--
pw-bot: cr
prev parent reply other threads:[~2026-11-15 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 6:43 [PATCH net-next v2] net: phy: motorcomm: add YT8831 2.5G PHY support Frank.sae
2026-11-15 19:05 ` 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=20261115110538.20b35287@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