From: kernel test robot <lkp@intel.com>
To: Atish Patra <atish.patra@wdc.com>
Cc: kbuild-all@lists.01.org, Atish Patra <Atish.Patra@wdc.com>,
linux-kernel@vger.kernel.org, Anup Patel <anup@brainfault.org>,
linux-doc@vger.kernel.org
Subject: [atishp04:sbi_pmu_v6 12/17] 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: Sun, 20 Feb 2022 18:17:22 +0800 [thread overview]
Message-ID: <202202201838.kdXweR8L-lkp@intel.com> (raw)
tree: https://github.com/atishp04/linux sbi_pmu_v6
head: 876094386d4f915d81ec2ee5b8b412987a10d808
commit: 9cba22b308da91d7cf0781fcc18b3ad34abdf9b0 [12/17] RISC-V: Add a simple platform driver for RISC-V legacy perf
config: riscv-allyesconfig (https://download.01.org/0day-ci/archive/20220220/202202201838.kdXweR8L-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 11.2.0
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
# https://github.com/atishp04/linux/commit/9cba22b308da91d7cf0781fcc18b3ad34abdf9b0
git remote add atishp04 https://github.com/atishp04/linux
git fetch --no-tags atishp04 sbi_pmu_v6
git checkout 9cba22b308da91d7cf0781fcc18b3ad34abdf9b0
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross 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, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-20 10:17 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=202202201838.kdXweR8L-lkp@intel.com \
--to=lkp@intel.com \
--cc=anup@brainfault.org \
--cc=atish.patra@wdc.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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).