linux-phy.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Liam Beguin <liambeguin@gmail.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
	linux-phy@lists.infradead.org, Roger Quadros <rogerq@ti.com>,
	Liam Beguin <lvb@xiphos.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6] phy: ti: omap-usb2: Fix the kernel-doc style
Date: Sat, 20 Nov 2021 12:10:18 -0500	[thread overview]
Message-ID: <YZkr+vwyiIfKx2Nc@shaak> (raw)
In-Reply-To: <20211116103951.34482-5-vkoul@kernel.org>

Hi Vinod,

On Tue, Nov 16, 2021 at 04:09:50PM +0530, Vinod Koul wrote:
> The documentation uses incorrect style, so fix that.
> 
> drivers/phy/ti/phy-omap-usb2.c:102: warning: Function parameter or member 'comparator' not described in 'omap_usb2_set_comparator'
> 
> While at it, use a single line for function description
> 
> Signed-off-by: Vinod Koul <vkoul@kernel.org>
> ---
>  drivers/phy/ti/phy-omap-usb2.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/phy/ti/phy-omap-usb2.c b/drivers/phy/ti/phy-omap-usb2.c
> index ebceb1520ce8..2102b7f73ffa 100644
> --- a/drivers/phy/ti/phy-omap-usb2.c
> +++ b/drivers/phy/ti/phy-omap-usb2.c
> @@ -89,9 +89,9 @@ static inline void omap_usb_writel(void __iomem *addr, unsigned int offset,
>  }
>  
>  /**
> - * omap_usb2_set_comparator - links the comparator present in the system with
> - *	this phy
> - * @comparator - the companion phy(comparator) for this phy
> + * omap_usb2_set_comparator - links the comparator present in the system with this phy

I missed it before but as Bjorn pointed out in this thread, it appears
the function name should end with parentheses.

Cheers,
Liam

> + *
> + * @comparator:  the companion phy(comparator) for this phy
>   *
>   * The phy companion driver should call this API passing the phy_companion
>   * filled with set_vbus and start_srp to be used by usb phy.
> -- 
> 2.31.1
> 
> 
> -- 
> linux-phy mailing list
> linux-phy@lists.infradead.org
> https://lists.infradead.org/mailman/listinfo/linux-phy

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

  parent reply	other threads:[~2021-11-20 17:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 10:39 [PATCH 1/6] phy: mvebu-cp110-utmi: Fix kernel-doc warns Vinod Koul
2021-11-16 10:39 ` [PATCH 2/6] phy: qualcomm: ipq806x-usb: Fix kernel-doc style Vinod Koul
2021-11-16 23:38   ` Randy Dunlap
2021-11-18  0:18   ` Bjorn Andersson
2021-11-20  6:00     ` Vinod Koul
2021-11-16 10:39 ` [PATCH 3/6] phy: qualcomm: qmp: Add missing struct documentation Vinod Koul
2021-11-18  0:19   ` Bjorn Andersson
2021-11-16 10:39 ` [PATCH 4/6] phy: qualcomm: usb-hsic: Fix the kernel-doc warn Vinod Koul
2021-11-18  0:20   ` Bjorn Andersson
2021-11-16 10:39 ` [PATCH 5/6] phy: ti: omap-usb2: Fix the kernel-doc style Vinod Koul
2021-11-16 16:43   ` Liam Beguin
2021-11-20 17:10   ` Liam Beguin [this message]
2021-11-16 10:39 ` [PATCH 6/6] phy: ti: tusb1210: Fix the kernel-doc warn Vinod Koul
2021-11-16 16:39   ` Liam Beguin

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=YZkr+vwyiIfKx2Nc@shaak \
    --to=liambeguin@gmail.com \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=lvb@xiphos.com \
    --cc=rogerq@ti.com \
    --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;
as well as URLs for NNTP newsgroup(s).