From: Pavel Machek <pavel@ucw.cz>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
Sebastian Reichel <sre@kernel.org>,
Aditya Srivastava <yashsri421@gmail.com>,
Kai Vehmanen <kai.vehmanen@nokia.com>
Subject: Re: [PATCH] HSI: cmt_speech: unmark comments as kernel-doc
Date: Sun, 22 Aug 2021 19:18:43 +0200 [thread overview]
Message-ID: <20210822171841.GA22647@duo.ucw.cz> (raw)
In-Reply-To: <20210822163838.15964-1-rdunlap@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
On Sun 2021-08-22 09:38:38, Randy Dunlap wrote:
> Fix build warnings from the kernel test robot:
>
> drivers/hsi/clients/cmt_speech.c:831: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
> * Block until pending data transfers have completed.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Reported-by: kernel test robot <lkp@intel.com>
> Cc: Sebastian Reichel <sre@kernel.org>
> Cc: Aditya Srivastava <yashsri421@gmail.com>
> Cc: Kai Vehmanen <kai.vehmanen@nokia.com>
Acked-by: Pavel Machek <pavel@ucw.cz>
Best regards,
Pavel
> @@ -827,7 +827,7 @@ static int check_buf_params(struct cs_hs
> return r;
> }
>
> -/**
> +/*
> * Block until pending data transfers have completed.
> */
> static int cs_hsi_data_sync(struct cs_hsi_iface *hi)
> @@ -850,7 +850,7 @@ static int cs_hsi_data_sync(struct cs_hs
> r = -ERESTARTSYS;
> goto out;
> }
> - /**
> + /*
> * prepare_to_wait must be called with hi->lock held
> * so that callbacks can check for waitqueue_active()
> */
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2021-08-22 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 16:38 Randy Dunlap
2021-08-22 17:18 ` Pavel Machek [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=20210822171841.GA22647@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=kai.vehmanen@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rdunlap@infradead.org \
--cc=sre@kernel.org \
--cc=yashsri421@gmail.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
all inboxes | Powered by JetHome®