From: kernel test robot <lkp@intel.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org
Subject: [kraxel:pcie-hotplug 1/1] drivers/pci/hotplug/pciehp_ctrl.c:25:1: warning: declaration specifier missing, defaulting to 'int'
Date: Fri, 5 Nov 2021 19:46:35 +0800 [thread overview]
Message-ID: <202111051927.BqTx6ErK-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3154 bytes --]
tree: git://git.kraxel.org/linux pcie-hotplug
head: 5d1d3bf197ff746e8b9760e7d5c3bdb0c6a73983
commit: 5d1d3bf197ff746e8b9760e7d5c3bdb0c6a73983 [1/1] pciehp: fast virtual unplug for VMs
config: arm64-randconfig-r026-20211104 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 847a6807332b13f43704327c2d30103ec0347c77)
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 arm64 cross compiling tool for clang build
# apt-get install binutils-aarch64-linux-gnu
git remote add kraxel git://git.kraxel.org/linux
git fetch --no-tags kraxel pcie-hotplug
git checkout 5d1d3bf197ff746e8b9760e7d5c3bdb0c6a73983
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash drivers/pci/hotplug/
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/pci/hotplug/pciehp_ctrl.c:25:35: error: unexpected type name 'bool': expected identifier
module_param(fast_virtual_unplug, bool, 0644);
^
drivers/pci/hotplug/pciehp_ctrl.c:25:41: error: expected identifier
module_param(fast_virtual_unplug, bool, 0644);
^
>> drivers/pci/hotplug/pciehp_ctrl.c:25:1: warning: declaration specifier missing, defaulting to 'int'
module_param(fast_virtual_unplug, bool, 0644);
^
int
drivers/pci/hotplug/pciehp_ctrl.c:25:13: error: this function declaration is not a prototype [-Werror,-Wstrict-prototypes]
module_param(fast_virtual_unplug, bool, 0644);
^
void
drivers/pci/hotplug/pciehp_ctrl.c:26:39: error: expected identifier
MODULE_PARM_DESC(fast_virtual_unplug, "Fast unplug (don't wait 5 seconds) for virtual machines.");
^
drivers/pci/hotplug/pciehp_ctrl.c:26:1: warning: declaration specifier missing, defaulting to 'int'
MODULE_PARM_DESC(fast_virtual_unplug, "Fast unplug (don't wait 5 seconds) for virtual machines.");
^
int
drivers/pci/hotplug/pciehp_ctrl.c:26:17: error: this function declaration is not a prototype [-Werror,-Wstrict-prototypes]
MODULE_PARM_DESC(fast_virtual_unplug, "Fast unplug (don't wait 5 seconds) for virtual machines.");
^
void
2 warnings and 5 errors generated.
vim +/int +25 drivers/pci/hotplug/pciehp_ctrl.c
23
24 static bool fast_virtual_unplug = true;
> 25 module_param(fast_virtual_unplug, bool, 0644);
26 MODULE_PARM_DESC(fast_virtual_unplug, "Fast unplug (don't wait 5 seconds) for virtual machines.");
27
---
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: 44351 bytes --]
reply other threads:[~2021-11-05 11:47 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=202111051927.BqTx6ErK-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
/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
all inboxes | Powered by JetHome®