From: Bagas Sanjaya <[email protected]>
To: Palmer Dabbelt <[email protected]>, Atish Patra <[email protected]>
Cc: [email protected], [email protected], [email protected],
[email protected], [email protected]
Subject: Re: [ammarfaizi2-block:palmer/linux/riscv-pmu 13/15] drivers/perf/riscv_pmu_sbi.c:498: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
Date: Wed, 23 Mar 2022 19:18:51 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <mhng-cc3dade0-37d7-4832-bb05-c23669599378@palmer-ri-x1c9>
On 23/03/22 05.06, Palmer Dabbelt wrote:
>> All warnings (new ones prefixed by >>):
>>
>> drivers/perf/riscv_pmu_sbi.c:42: warning: cannot understand function prototype: 'union sbi_pmu_ctr_info *pmu_ctr_list; '
>
> Looks like that's just fallout from the ** comments.
>
>>>> drivers/perf/riscv_pmu_sbi.c:498: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
>
> I sent a fix for this one, there were a handful of them. Sorry I missed that.
>
I have already sent the fix for vcpu_sbi.c at [1], but forgot to
Cc: [email protected] (I put it on To: instead), can you please pick it up?
[1]: https://lore.kernel.org/linux-doc/[email protected]/
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-03-23 12:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 13:24 [ammarfaizi2-block:palmer/linux/riscv-pmu 13/15] drivers/perf/riscv_pmu_sbi.c:498: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst kernel test robot
2022-03-22 22:06 ` Palmer Dabbelt
2022-03-23 12:18 ` Bagas Sanjaya [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-22 8:23 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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