linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Asutosh Das <asutoshd@codeaurora.org>
Cc: kbuild-all@lists.01.org,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Can Guo <cang@codeaurora.org>,
	linux-doc@vger.kernel.org
Subject: [mkp-scsi:queue 12/14] drivers/scsi/ufs/ufshcd.c:9710: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
Date: Tue, 11 May 2021 06:01:06 +0800	[thread overview]
Message-ID: <202105110657.C5VB1bgQ-lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git queue
head:   cfaad0f79d37bceb15a9a6d1c3b6c8c5ff5364b5
commit: edf377c8db4aaf31e2c15260d3ce69b9572673f8 [12/14] scsi: ufs: core: Enable power management for wlun
config: microblaze-randconfig-r035-20210510 (attached as .config)
compiler: microblaze-linux-gcc (GCC) 9.3.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://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=edf377c8db4aaf31e2c15260d3ce69b9572673f8
        git remote add mkp-scsi https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git
        git fetch --no-tags mkp-scsi queue
        git checkout edf377c8db4aaf31e2c15260d3ce69b9572673f8
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross W=1 ARCH=microblaze 

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/scsi/ufs/ufshcd.c:9667: warning: cannot understand function prototype: 'struct scsi_driver ufs_dev_wlun_template = '
>> drivers/scsi/ufs/ufshcd.c:9710: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * Describes the ufs rpmb wlun.


vim +9710 drivers/scsi/ufs/ufshcd.c

  9708	
  9709	/**
> 9710	 * Describes the ufs rpmb wlun.
  9711	 * Used only to send uac.
  9712	 */
  9713	static struct scsi_driver ufs_rpmb_wlun_template = {
  9714		.gendrv = {
  9715			.name = "ufs_rpmb_wlun",
  9716			.owner = THIS_MODULE,
  9717			.probe = ufshcd_rpmb_probe,
  9718			.pm = &ufs_rpmb_pm_ops,
  9719		},
  9720	};
  9721	

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

             reply	other threads:[~2021-05-10 22:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 22:01 kernel test robot [this message]
2021-05-11  0:15 [mkp-scsi:queue 12/14] drivers/scsi/ufs/ufshcd.c:9710: 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=202105110657.C5VB1bgQ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=adrian.hunter@intel.com \
    --cc=asutoshd@codeaurora.org \
    --cc=cang@codeaurora.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).