From: kernel test robot <lkp@intel.com>
To: Atish Patra <atish.patra@wdc.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
linux-kernel@vger.kernel.org,
Palmer Dabbelt <palmer@rivosinc.com>,
Anup Patel <anup@brainfault.org>,
linux-doc@vger.kernel.org
Subject: [ammarfaizi2-block:palmer/linux/riscv-pmu 10/15] drivers/perf/riscv_pmu_legacy.c:76: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
Date: Tue, 22 Mar 2022 15:32:50 +0800 [thread overview]
Message-ID: <202203221500.ajQCd6Bp-lkp@intel.com> (raw)
tree: https://github.com/ammarfaizi2/linux-block palmer/linux/riscv-pmu
head: 33363c336516e4beb9dd7e8265b369ff96d07dcb
commit: 9b3e150e310ee71d7bae1e31c38a300cfa5e951b [10/15] RISC-V: Add a simple platform driver for RISC-V legacy perf
config: riscv-randconfig-r042-20220320 (https://download.01.org/0day-ci/archive/20220322/202203221500.ajQCd6Bp-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 85e9b2687a13d1908aa86d1b89c5ce398a06cd39)
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/ammarfaizi2/linux-block/commit/9b3e150e310ee71d7bae1e31c38a300cfa5e951b
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block palmer/linux/riscv-pmu
git checkout 9b3e150e310ee71d7bae1e31c38a300cfa5e951b
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash drivers/perf/
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:76: 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 +76 drivers/perf/riscv_pmu_legacy.c
74
75 /**
> 76 * This is just a simple implementation to allow legacy implementations
77 * compatible with new RISC-V PMU driver framework.
78 * This driver only allows reading two counters i.e CYCLE & INSTRET.
79 * However, it can not start or stop the counter. Thus, it is not very useful
80 * will be removed in future.
81 */
82 static void pmu_legacy_init(struct riscv_pmu *pmu)
83 {
84 pr_info("Legacy PMU implementation is available\n");
85
86 pmu->num_counters = RISCV_PMU_LEGACY_NUM_CTR;
87 pmu->ctr_start = pmu_legacy_ctr_start;
88 pmu->ctr_stop = NULL;
89 pmu->event_map = pmu_legacy_event_map;
90 pmu->ctr_get_idx = pmu_legacy_ctr_get_idx;
91 pmu->ctr_get_width = NULL;
92 pmu->ctr_clear_idx = NULL;
93 pmu->ctr_read = pmu_legacy_read_ctr;
94
95 perf_pmu_register(&pmu->pmu, "cpu", PERF_TYPE_RAW);
96 }
97
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-03-22 7:33 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=202203221500.ajQCd6Bp-lkp@intel.com \
--to=lkp@intel.com \
--cc=anup@brainfault.org \
--cc=atish.patra@wdc.com \
--cc=gwml@vger.gnuweeb.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=palmer@rivosinc.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