From: kernel test robot <lkp@intel.com>
To: Atish Patra <atish.patra@wdc.com>
Cc: clang-built-linux@googlegroups.com, kbuild-all@lists.01.org,
Atish Patra <Atish.Patra@wdc.com>,
linux-doc@vger.kernel.org
Subject: [atishp04:sbi_pmu_v3 13/16] drivers/perf/riscv_pmu_legacy.c:74: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
Date: Tue, 29 Jun 2021 21:44:08 +0800 [thread overview]
Message-ID: <202106292102.SqKoJ2S6-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1720 bytes --]
tree: https://github.com/atishp04/linux sbi_pmu_v3
head: 73c9714a1d4de79fee9085c767688f27f7cd8f44
commit: 892d098b5c8709d64898638b744a482873a9a349 [13/16] RISC-V: Add a simple platform driver for RISC-V legacy perf
config: riscv-randconfig-r005-20210628 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project aad87328fabff9382bac0b452c83934515e6d0c8)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install riscv cross compiling tool for clang build
# apt-get install binutils-riscv64-linux-gnu
# https://github.com/atishp04/linux/commit/892d098b5c8709d64898638b744a482873a9a349
git remote add atishp04 https://github.com/atishp04/linux
git fetch --no-tags atishp04 sbi_pmu_v3
git checkout 892d098b5c8709d64898638b744a482873a9a349
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=riscv
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 >>):
>> drivers/perf/riscv_pmu_legacy.c:74: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* This is just a simple implementation to allow legacy implementations
vim +74 drivers/perf/riscv_pmu_legacy.c
72
73 /**
> 74 * This is just a simple implementation to allow legacy implementations
---
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: 28437 bytes --]
reply other threads:[~2021-06-29 13:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202106292102.SqKoJ2S6-lkp@intel.com \
--to=lkp@intel.com \
--cc=atish.patra@wdc.com \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-doc@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).