From: Randy Dunlap <rdunlap@infradead.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
Aditya Srivastava <yashsri421@gmail.com>
Subject: Re: [PATCH v2] HSI: cmt_speech: unmark comments as kernel-doc
Date: Thu, 30 Sep 2021 11:45:38 -0700 [thread overview]
Message-ID: <5465ad4d-8999-ad3d-8858-c2e1b8b463f8@infradead.org> (raw)
In-Reply-To: <20210930170138.xlspkxshgr4od7t6@earth.universe>
On 9/30/21 10:01 AM, Sebastian Reichel wrote:
> Hi,
>
> On Tue, Sep 28, 2021 at 12:52:03PM -0700, Randy Dunlap wrote:
>> On 9/28/21 11:57 AM, Pavel Machek wrote:
>>> Hi!
>>>
>>>> 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>
>>>> Acked-by: Pavel Machek <pavel@ucw.cz>
>>>
>>> If noone applies it, you may want to send it to akpm, he's often
>>> helpful in pushing similar patches.
>>
>> Yes, good idea. Thanks.
>
> Looks like I missed v1. The patch LGTM and I can apply it to the hsi tree.
> If you already sent it to akpm, that's also fine. Not much is happening in
> HSI nowadays and it probably will be the only patch for the next cycle.
You go ahead with it, please.
thanks.
--
~Randy
prev parent reply other threads:[~2021-09-30 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 18:35 [PATCH v2] HSI: cmt_speech: unmark comments as kernel-doc Randy Dunlap
2021-09-28 18:57 ` Pavel Machek
2021-09-28 19:52 ` Randy Dunlap
2021-09-30 17:01 ` Sebastian Reichel
2021-09-30 18:45 ` Randy Dunlap [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=5465ad4d-8999-ad3d-8858-c2e1b8b463f8@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=pavel@ucw.cz \
--cc=sebastian.reichel@collabora.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.