From: Borislav Petkov <bp@alien8.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
Guenter Roeck <linux@roeck-us.net>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Yash Shah <yash.shah@sifive.com>,
linux-edac@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH] EDAC/sifive: fix non-kernel-doc comment
Date: Sun, 5 Dec 2021 20:29:45 +0100 [thread overview]
Message-ID: <Ya0TKe1m+WfoCFWv@zn.tnic> (raw)
In-Reply-To: <20211201030913.10283-1-rdunlap@infradead.org>
On Tue, Nov 30, 2021 at 07:09:13PM -0800, Randy Dunlap wrote:
> scripts/kernel-doc complains about a comment that begins with "/**"
> but is not in kernel-doc format, so correct it.
>
> Prevents this warning:
>
> drivers/edac/sifive_edac.c:23: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
> * EDAC error callback
>
> Fixes: 91abaeaaff35 ("EDAC/sifive: Add EDAC platform driver for SiFive SoCs")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Reported-by: kernel test robot <lkp@intel.com>
> Cc: Guenter Roeck <linux@roeck-us.net>
> Cc: Palmer Dabbelt <palmerdabbelt@google.com>
> Cc: Yash Shah <yash.shah@sifive.com>
> Cc: linux-edac@vger.kernel.org
> Cc: Borislav Petkov <bp@alien8.de>
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Cc: Tony Luck <tony.luck@intel.com>
> ---
Applied, thanks.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2021-12-05 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 3:09 [PATCH] EDAC/sifive: fix non-kernel-doc comment Randy Dunlap
2021-12-05 19:29 ` Borislav Petkov [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=Ya0TKe1m+WfoCFWv@zn.tnic \
--to=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkp@intel.com \
--cc=mchehab@kernel.org \
--cc=palmerdabbelt@google.com \
--cc=rdunlap@infradead.org \
--cc=tony.luck@intel.com \
--cc=yash.shah@sifive.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