All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Atish Patra <atish.patra@wdc.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-kernel@vger.kernel.org, Anup Patel <anup@brainfault.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	linux-doc@vger.kernel.org
Subject: [avpatel:riscv_aclint_v3 17/31] arch/riscv/kvm/vcpu_sbi.c:3: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
Date: Sun, 29 Aug 2021 20:06:57 +0800	[thread overview]
Message-ID: <202108292053.gnEmJFN7-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1764 bytes --]

tree:   https://github.com/avpatel/linux.git riscv_aclint_v3
head:   fd979f4acceee515c8f7a7e9b95a6072f9146bef
commit: 41555c143616bbdbeca0073d59eee697a12cd4f3 [17/31] RISC-V: KVM: Add SBI v0.1 support
config: riscv-randconfig-r036-20210829 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 4e1a164d7bd53653f79decc121afe784d2fde0a7)
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/avpatel/linux/commit/41555c143616bbdbeca0073d59eee697a12cd4f3
        git remote add avpatel https://github.com/avpatel/linux.git
        git fetch --no-tags avpatel riscv_aclint_v3
        git checkout 41555c143616bbdbeca0073d59eee697a12cd4f3
        # 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 >>):

>> arch/riscv/kvm/vcpu_sbi.c:3: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * Copyright (c) 2019 Western Digital Corporation or its affiliates.


vim +3 arch/riscv/kvm/vcpu_sbi.c

   > 3	 * Copyright (c) 2019 Western Digital Corporation or its affiliates.
     4	 *
     5	 * Authors:
     6	 *     Atish Patra <atish.patra@wdc.com>
     7	 */
     8	

---
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: 37296 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [avpatel:riscv_aclint_v3 17/31] arch/riscv/kvm/vcpu_sbi.c:3: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
Date: Sun, 29 Aug 2021 20:06:57 +0800	[thread overview]
Message-ID: <202108292053.gnEmJFN7-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1804 bytes --]

tree:   https://github.com/avpatel/linux.git riscv_aclint_v3
head:   fd979f4acceee515c8f7a7e9b95a6072f9146bef
commit: 41555c143616bbdbeca0073d59eee697a12cd4f3 [17/31] RISC-V: KVM: Add SBI v0.1 support
config: riscv-randconfig-r036-20210829 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 4e1a164d7bd53653f79decc121afe784d2fde0a7)
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/avpatel/linux/commit/41555c143616bbdbeca0073d59eee697a12cd4f3
        git remote add avpatel https://github.com/avpatel/linux.git
        git fetch --no-tags avpatel riscv_aclint_v3
        git checkout 41555c143616bbdbeca0073d59eee697a12cd4f3
        # 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 >>):

>> arch/riscv/kvm/vcpu_sbi.c:3: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * Copyright (c) 2019 Western Digital Corporation or its affiliates.


vim +3 arch/riscv/kvm/vcpu_sbi.c

   > 3	 * Copyright (c) 2019 Western Digital Corporation or its affiliates.
     4	 *
     5	 * Authors:
     6	 *     Atish Patra <atish.patra@wdc.com>
     7	 */
     8	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 37296 bytes --]

             reply	other threads:[~2021-08-29 12:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-29 12:06 kernel test robot [this message]
2021-08-29 12:06 ` [avpatel:riscv_aclint_v3 17/31] arch/riscv/kvm/vcpu_sbi.c:3: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst 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=202108292053.gnEmJFN7-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 \
    --cc=llvm@lists.linux.dev \
    --cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.