From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Bean Huo'" <huobean@gmail.com>, <avri.altman@wdc.com>,
<jejb@linux.ibm.com>, <martin.petersen@oracle.com>,
<beanhuo@micron.com>, <bvanassche@acm.org>,
<tomas.winkler@intel.com>, <cang@codeaurora.org>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] scsi: ufs: Fix a kernel-doc related formatting issue
Date: Mon, 31 May 2021 22:06:28 +0530 [thread overview]
Message-ID: <049f01d7563b$1ca20b80$55e62280$@samsung.com> (raw)
In-Reply-To: <20210531163122.451375-1-huobean@gmail.com>
Hi Bean,
> -----Original Message-----
> From: Bean Huo <huobean@gmail.com>
> Sent: 31 May 2021 22:01
> To: alim.akhtar@samsung.com; avri.altman@wdc.com; jejb@linux.ibm.com;
> martin.petersen@oracle.com; beanhuo@micron.com;
> bvanassche@acm.org; tomas.winkler@intel.com; cang@codeaurora.org
> Cc: linux-scsi@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: [PATCH] scsi: ufs: Fix a kernel-doc related formatting issue
>
> From: Bean Huo <beanhuo@micron.com>
>
> Fix the following W=1 kernel build warning:
>
> drivers/scsi/ufs/ufshcd.c:9773: warning: This comment starts with '/**',
but
> isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
>
> Signed-off-by: Bean Huo <beanhuo@micron.com>
> ---
Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
> drivers/scsi/ufs/ufshcd.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
.
.
.
> --
> 2.25.1
next prev parent reply other threads:[~2021-05-31 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210531163136epcas5p33bc53d90af17333be4b2805d7ad3155e@epcas5p3.samsung.com>
2021-05-31 16:31 ` [PATCH] scsi: ufs: Fix a kernel-doc related formatting issue Bean Huo
2021-05-31 16:36 ` Alim Akhtar [this message]
2021-05-31 21:03 ` Bart Van Assche
2021-06-02 3:43 ` Martin K. Petersen
2021-06-08 3:05 ` Martin K. Petersen
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='049f01d7563b$1ca20b80$55e62280$@samsung.com' \
--to=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=huobean@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=tomas.winkler@intel.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