From: kernel test robot <lkp@intel.com>
To: Aditya Srivastava <yashsri421@gmail.com>, corbet@lwn.net
Cc: kbuild-all@lists.01.org, yashsri421@gmail.com,
lukas.bulwahn@gmail.com,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts: kernel-doc: add warning for comment not following kernel-doc syntax
Date: Mon, 29 Mar 2021 20:49:20 +0800 [thread overview]
Message-ID: <202103292018.qaDqrjCt-lkp@intel.com> (raw)
In-Reply-To: <20210329092945.13152-1-yashsri421@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3205 bytes --]
Hi Aditya,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on lwn/docs-next]
[also build test WARNING on linus/master v5.12-rc5 next-20210329]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Aditya-Srivastava/scripts-kernel-doc-add-warning-for-comment-not-following-kernel-doc-syntax/20210329-173213
base: git://git.lwn.net/linux-2.6 docs-next
config: i386-tinyconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/274a7b0af9aa2846ed0a5b2096e07fe76e47fe29
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Aditya-Srivastava/scripts-kernel-doc-add-warning-for-comment-not-following-kernel-doc-syntax/20210329-173213
git checkout 274a7b0af9aa2846ed0a5b2096e07fe76e47fe29
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/x86/kernel/i8259.c:234: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* ELCR registers (0x4d0, 0x4d1) control edge/level of IRQ
--
>> arch/x86/lib/cmdline.c:17: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Find a boolean option (like quiet,noapic,nosmp....)
--
arch/x86/lib/msr.c:40: warning: expecting prototype for Read an MSR with error handling(). Prototype was for msr_read() instead
arch/x86/lib/msr.c:58: warning: expecting prototype for Write an MSR with error handling(). Prototype was for msr_write() instead
>> arch/x86/lib/msr.c:91: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Set @bit in a MSR @msr.
arch/x86/lib/msr.c:104: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Clear @bit in a MSR @msr.
vim +234 arch/x86/kernel/i8259.c
4305df947ca1fd Thomas Gleixner 2010-09-28 231
21fd5132b223a1 Pavel Machek 2008-05-21 232 static char irq_trigger[2];
21fd5132b223a1 Pavel Machek 2008-05-21 233 /**
21fd5132b223a1 Pavel Machek 2008-05-21 @234 * ELCR registers (0x4d0, 0x4d1) control edge/level of IRQ
21fd5132b223a1 Pavel Machek 2008-05-21 235 */
21fd5132b223a1 Pavel Machek 2008-05-21 236 static void restore_ELCR(char *trigger)
21fd5132b223a1 Pavel Machek 2008-05-21 237 {
21fd5132b223a1 Pavel Machek 2008-05-21 238 outb(trigger[0], 0x4d0);
21fd5132b223a1 Pavel Machek 2008-05-21 239 outb(trigger[1], 0x4d1);
21fd5132b223a1 Pavel Machek 2008-05-21 240 }
21fd5132b223a1 Pavel Machek 2008-05-21 241
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 7346 bytes --]
next prev parent reply other threads:[~2021-03-29 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 9:29 [PATCH] scripts: kernel-doc: add warning for comment not following kernel-doc syntax Aditya Srivastava
2021-03-29 12:49 ` kernel test robot [this message]
2021-03-29 13:56 ` Jonathan Corbet
2021-03-29 15:10 ` Aditya Srivastava
2021-03-31 19:32 ` Jonathan Corbet
2021-04-03 12:43 ` Aditya Srivastava
2021-03-29 14:57 ` kernel test robot
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=202103292018.qaDqrjCt-lkp@intel.com \
--to=lkp@intel.com \
--cc=corbet@lwn.net \
--cc=kbuild-all@lists.01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox