From: Vinod Koul <vkoul@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
linux-phy@lists.infradead.org
Subject: Re: [PATCH] phy: ti: report 2 non-kernel-doc comments
Date: Tue, 16 Nov 2021 16:10:12 +0530 [thread overview]
Message-ID: <YZOKjDoOR0s/fKV4@matsya> (raw)
In-Reply-To: <20211115030559.13994-1-rdunlap@infradead.org>
On 14-11-21, 19:05, Randy Dunlap wrote:
> Do not use "/**" to begin a non-kernel-doc comment.
> Fixes these build warnings:
>
> drivers/phy/ti/phy-am654-serdes.c:3: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
> * PCIe SERDES driver for AM654x SoC
>
> drivers/phy/ti/phy-j721e-wiz.c:3: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
> * Wrapper driver for SERDES used in J721E
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2021-11-16 10:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 3:05 [PATCH] phy: ti: report 2 non-kernel-doc comments Randy Dunlap
2021-11-16 10:40 ` Vinod Koul [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=YZOKjDoOR0s/fKV4@matsya \
--to=vkoul@kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=lkp@intel.com \
--cc=rdunlap@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