From: kernel test robot <lkp@intel.com>
To: Megha Dey <megha.dey@intel.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org
Subject: [meghadey-crypto:dmsix_new 3/10] drivers/pci/probe.c:2265:19: error: no member named 'msix_mutex' in 'struct pci_dev'
Date: Thu, 2 Sep 2021 00:37:12 +0800 [thread overview]
Message-ID: <202109020005.5l2w6kd1-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2093 bytes --]
tree: https://github.com/meghadey/crypto dmsix_new
head: 9c6d0a5aa6197d3927bb41a1b675d150a0a8b5c8
commit: 4dd07c671581782c63ea7c71cd9dad746b73dac0 [3/10] mutex
config: x86_64-randconfig-r024-20210831 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 4b1fde8a2b681dad2ce0c082a5d6422caa06b0bc)
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://github.com/meghadey/crypto/commit/4dd07c671581782c63ea7c71cd9dad746b73dac0
git remote add meghadey-crypto https://github.com/meghadey/crypto
git fetch --no-tags meghadey-crypto dmsix_new
git checkout 4dd07c671581782c63ea7c71cd9dad746b73dac0
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/pci/probe.c:2265:19: error: no member named 'msix_mutex' in 'struct pci_dev'
mutex_init(&dev->msix_mutex);
~~~ ^
include/linux/mutex.h:105:16: note: expanded from macro 'mutex_init'
__mutex_init((mutex), #mutex, &__key); \
^~~~~
1 error generated.
vim +2265 drivers/pci/probe.c
2255
2256 struct pci_dev *pci_alloc_dev(struct pci_bus *bus)
2257 {
2258 struct pci_dev *dev;
2259
2260 dev = kzalloc(sizeof(struct pci_dev), GFP_KERNEL);
2261 if (!dev)
2262 return NULL;
2263
2264 INIT_LIST_HEAD(&dev->bus_list);
> 2265 mutex_init(&dev->msix_mutex);
2266 dev->dev.type = &pci_dev_type;
2267 dev->bus = pci_bus_get(bus);
2268
2269 return dev;
2270 }
2271 EXPORT_SYMBOL(pci_alloc_dev);
2272
---
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: 30793 bytes --]
reply other threads:[~2021-09-01 16:37 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=202109020005.5l2w6kd1-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=megha.dey@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