Linux-PHY Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Vinod Koul" <vkoul@kernel.org>
Cc: vkoul@kernel.org, neil.armstrong@linaro.org, olteanv@gmail.com,
	linux-phy@lists.infradead.org
Subject: Re: [PATCH] phy: rockchip: inno-usb2: fix missing kernel-doc
Date: Tue, 19 May 2026 11:19:49 +0000	[thread overview]
Message-ID: <20260519111949.CD491C2BCB3@smtp.kernel.org> (raw)
In-Reply-To: <20260519110134.282428-1-vkoul@kernel.org>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] The commit adds a kernel-doc description for a struct member `clkout_ctl_phy` that does not exist in `struct rockchip_usb2phy_cfg`.
- [Low] The `Fixes:` tag in the commit message is malformed due to an extraneous trailing double quote.
--

commit 532f790b604de504c1843006c2bda7a4bcb6937e
Author: Vinod Koul <vkoul@kernel.org>

phy: rockchip: inno-usb2: fix missing kernel-doc

This commit documents the clkout_ctl_phy variable in the kernel-doc block
to resolve a missing description warning.

> Fixes: 2775541de058 ("phy: rockchip: inno-usb2: Add clkout_ctl_phy support")"

This isn't a bug, but there is an extraneous trailing double quote at the end
of the Fixes tag.

> diff --git a/drivers/phy/rockchip/phy-rockchip-inno-usb2.c b/drivers/phy/rockchip/phy-rockchip-inno-usb2.c
> index 8f4c08e599aa2..a69e7dbe18195 100644
> --- a/drivers/phy/rockchip/phy-rockchip-inno-usb2.c
> +++ b/drivers/phy/rockchip/phy-rockchip-inno-usb2.c
> @@ -171,6 +171,7 @@ struct rockchip_usb2phy_port_cfg {
>   * @num_ports: specify how many ports that the phy has.
>   * @phy_tuning: phy default parameters tuning.
>   * @clkout_ctl: keep on/turn off output clk of phy.
> + * @clkout_ctl_phy: output clk phy registers

Is the clkout_ctl_phy field present in the structure definition here?

If the structure is missing this member, adding the description will
trigger an excess struct member warning instead.

>   * @port_cfgs: usb-phy port configurations.
>   * @chg_det: charger detection registers.
>   */

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260519110134.282428-1-vkoul@kernel.org?part=1

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

  reply	other threads:[~2026-05-19 11:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19 11:01 [PATCH] phy: rockchip: inno-usb2: fix missing kernel-doc Vinod Koul
2026-05-19 11:19 ` sashiko-bot [this message]
2026-05-20  6:03   ` Vinod Koul

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=20260519111949.CD491C2BCB3@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=olteanv@gmail.com \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vkoul@kernel.org \
    /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