public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
	Aditya Srivastava <yashsri421@gmail.com>,
	linux-input@vger.kernel.org,
	Haojian Zhuang <haojian.zhuang@gmail.com>
Subject: Re: [PATCH] input/misc: max8925_onkey.c: don't mark comment as kernel-doc
Date: Fri, 15 Oct 2021 22:09:24 -0700	[thread overview]
Message-ID: <YWpehFWNrtyTKkGc@google.com> (raw)
In-Reply-To: <20211002045943.9406-1-rdunlap@infradead.org>

On Fri, Oct 01, 2021 at 09:59:43PM -0700, Randy Dunlap wrote:
> Change the comment to a normal (non-kernel-doc) comment to avoid
> these kernel-doc warnings:
> 
> max8925_onkey.c:2: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
>  * MAX8925 ONKEY driver
> max8925_onkey.c:2: warning: missing initial short description on line:
>  * MAX8925 ONKEY driver
> 
> Fixes: 3734574cac100 ("Input: enable onkey driver of max8925")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Reported-by: kernel test robot <lkp@intel.com>
> Cc: Aditya Srivastava <yashsri421@gmail.com>
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Cc: linux-input@vger.kernel.org
> Cc: Haojian Zhuang <haojian.zhuang@gmail.com>

Applied, thank you.

-- 
Dmitry

      reply	other threads:[~2021-10-16  5:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-02  4:59 [PATCH] input/misc: max8925_onkey.c: don't mark comment as kernel-doc Randy Dunlap
2021-10-16  5:09 ` Dmitry Torokhov [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=YWpehFWNrtyTKkGc@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=haojian.zhuang@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=rdunlap@infradead.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