From: Lu Baolu <baolu.lu@linux.intel.com>
To: kernel test robot <lkp@intel.com>
Cc: baolu.lu@linux.intel.com, kbuild-all@lists.01.org,
clang-built-linux@googlegroups.com,
Linux Memory Management List <linux-mm@kvack.org>,
Joerg Roedel <jroedel@suse.de>, Fenghua Yu <fenghua.yu@intel.com>
Subject: Re: [linux-next:master 8472/9209] drivers/iommu/intel/perf.c:16: warning: expecting prototype for perf.c(). Prototype was for DEFINE_SPINLOCK() instead
Date: Tue, 15 Jun 2021 11:18:24 +0800 [thread overview]
Message-ID: <09a11577-5c2d-808d-ac70-8d546ef43199@linux.intel.com> (raw)
In-Reply-To: <202106121952.9eBLxaDd-lkp@intel.com>
On 6/12/21 7:47 PM, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 25fe90f43fa312213b653dc1f12fd2d80f855883
> commit: 456bb0b97f00fe8defba155c0a4c48d951635395 [8472/9209] iommu/vt-d: Expose latency monitor data through debugfs
> config: x86_64-randconfig-a006-20210612 (attached as .config)
> compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project d2012d965d60c3258b3a69d024491698f8aec386)
> 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 x86_64 cross compiling tool for clang build
> # apt-get install binutils-x86-64-linux-gnu
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=456bb0b97f00fe8defba155c0a4c48d951635395
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout 456bb0b97f00fe8defba155c0a4c48d951635395
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
>
> 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/iommu/intel/perf.c:16: warning: Function parameter or member 'latency_lock' not described in 'DEFINE_SPINLOCK'
>>> drivers/iommu/intel/perf.c:16: warning: expecting prototype for perf.c(). Prototype was for DEFINE_SPINLOCK() instead
This seems to be a kernel doc warning and should be fixed in the header
file for DEFINE_SPINLOCK. Did I miss anything?
DEFINE_SPINLOCK is used everywhere, perhaps we need to add some comments
around it?
Best regards,
baolu
>
>
> vim +16 drivers/iommu/intel/perf.c
>
> 55ee5e67a59a1b Lu Baolu 2021-06-10 15
> 55ee5e67a59a1b Lu Baolu 2021-06-10 @16 static DEFINE_SPINLOCK(latency_lock);
> 55ee5e67a59a1b Lu Baolu 2021-06-10 17
>
> :::::: The code at line 16 was first introduced by commit
> :::::: 55ee5e67a59a1b6f388d7a1c7b24022145f47a3e iommu/vt-d: Add common code for dmar latency performance monitors
>
> :::::: TO: Lu Baolu <baolu.lu@linux.intel.com>
> :::::: CC: Joerg Roedel <jroedel@suse.de>
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>
prev parent reply other threads:[~2021-06-15 3:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-12 11:47 [linux-next:master 8472/9209] drivers/iommu/intel/perf.c:16: warning: expecting prototype for perf.c(). Prototype was for DEFINE_SPINLOCK() instead kernel test robot
2021-06-15 3:18 ` Lu Baolu [this message]
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=09a11577-5c2d-808d-ac70-8d546ef43199@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=clang-built-linux@googlegroups.com \
--cc=fenghua.yu@intel.com \
--cc=jroedel@suse.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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).