From: Vinod Koul <vkoul@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
linux-phy@lists.infradead.org, Andy Gross <agross@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/6] phy: qualcomm: ipq806x-usb: Fix kernel-doc style
Date: Sat, 20 Nov 2021 11:30:23 +0530 [thread overview]
Message-ID: <YZiO92inoiTapw0o@matsya> (raw)
In-Reply-To: <YZWbxdnfHKdCI/hz@builder.lan>
On 17-11-21, 18:18, Bjorn Andersson wrote:
> On Tue 16 Nov 04:39 CST 2021, Vinod Koul wrote:
>
> > The functions are documented but there were style issues, so fix
> > the style and add missing description for phy_dwc3
> >
> > drivers/phy/qualcomm/phy-qcom-ipq806x-usb.c:130:
> > drivers/phy/qualcomm/phy-qcom-ipq806x-usb.c:174:
> > drivers/phy/qualcomm/phy-qcom-ipq806x-usb.c:212: warning:
> > This comment starts with '/**', but isn't a kernel-doc comment.
> > Refer Documentation/doc-guide/kernel-doc.rst
> >
> > Signed-off-by: Vinod Koul <vkoul@kernel.org>
> > ---
> > drivers/phy/qualcomm/phy-qcom-ipq806x-usb.c | 26 +++++++++++----------
> > 1 file changed, 14 insertions(+), 12 deletions(-)
> >
> > diff --git a/drivers/phy/qualcomm/phy-qcom-ipq806x-usb.c b/drivers/phy/qualcomm/phy-qcom-ipq806x-usb.c
> > index bfff0c8c9130..e1b8fa911416 100644
> > --- a/drivers/phy/qualcomm/phy-qcom-ipq806x-usb.c
> > +++ b/drivers/phy/qualcomm/phy-qcom-ipq806x-usb.c
> > @@ -127,12 +127,13 @@ struct phy_drvdata {
> > };
> >
> > /**
> > - * Write register and read back masked value to confirm it is written
> > + * usb_phy_write_readback - Write register and read back masked value to
>
> "Writing kernel-doc" indicates that you should have some parenthesis
> after that function.
Heh, it does not warn :(, will update this
>
> > + * confirm it is written
> > *
> > - * @base - QCOM DWC3 PHY base virtual address.
> > - * @offset - register offset.
> > - * @mask - register bitmask specifying what should be updated
> > - * @val - value to write.
> > + * @phy_dwc3: QCOM DWC3 PHY base virtual address.
>
> I guess this was "base" at some point? As you're fixing up the
> kerneldoc, it would be nice to correct this to say something like
> "usb_phy context".
Why did I miss this one :(, yeah will update this
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2021-11-20 6:00 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 [this message]
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
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=YZiO92inoiTapw0o@matsya \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=kishon@ti.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.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).