From: kernel test robot <lkp@intel.com> To: Megha Dey <megha.dey@intel.com> Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org Subject: [meghadey-crypto:dmsix_new 3/10] drivers/pci/probe.c:2265:24: error: 'struct pci_dev' has no member named 'msix_mutex' Date: Wed, 1 Sep 2021 17:17:46 +0800 [thread overview] Message-ID: <202109011740.Ui2f9smr-lkp@intel.com> (raw) [-- Attachment #1: Type: text/plain, Size: 2359 bytes --] tree: https://github.com/meghadey/crypto dmsix_new head: 9c6d0a5aa6197d3927bb41a1b675d150a0a8b5c8 commit: 4dd07c671581782c63ea7c71cd9dad746b73dac0 [3/10] mutex config: xtensa-randconfig-r033-20210831 (attached as .config) compiler: xtensa-linux-gcc (GCC) 11.2.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://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=gcc-11.2.0 make.cross O=build_dir ARCH=xtensa SHELL=/bin/bash drivers/pci/ 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 >>): In file included from include/linux/kernfs.h:12, from include/linux/sysfs.h:16, from include/linux/kobject.h:20, from include/linux/pci.h:35, from drivers/pci/probe.c:9: drivers/pci/probe.c: In function 'pci_alloc_dev': >> drivers/pci/probe.c:2265:24: error: 'struct pci_dev' has no member named 'msix_mutex' 2265 | mutex_init(&dev->msix_mutex); | ^~ include/linux/mutex.h:105:23: note: in definition of macro 'mutex_init' 105 | __mutex_init((mutex), #mutex, &__key); \ | ^~~~~ 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: 34471 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com> To: kbuild-all@lists.01.org Subject: [meghadey-crypto:dmsix_new 3/10] drivers/pci/probe.c:2265:24: error: 'struct pci_dev' has no member named 'msix_mutex' Date: Wed, 01 Sep 2021 17:17:46 +0800 [thread overview] Message-ID: <202109011740.Ui2f9smr-lkp@intel.com> (raw) [-- Attachment #1: Type: text/plain, Size: 2420 bytes --] tree: https://github.com/meghadey/crypto dmsix_new head: 9c6d0a5aa6197d3927bb41a1b675d150a0a8b5c8 commit: 4dd07c671581782c63ea7c71cd9dad746b73dac0 [3/10] mutex config: xtensa-randconfig-r033-20210831 (attached as .config) compiler: xtensa-linux-gcc (GCC) 11.2.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://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=gcc-11.2.0 make.cross O=build_dir ARCH=xtensa SHELL=/bin/bash drivers/pci/ 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 >>): In file included from include/linux/kernfs.h:12, from include/linux/sysfs.h:16, from include/linux/kobject.h:20, from include/linux/pci.h:35, from drivers/pci/probe.c:9: drivers/pci/probe.c: In function 'pci_alloc_dev': >> drivers/pci/probe.c:2265:24: error: 'struct pci_dev' has no member named 'msix_mutex' 2265 | mutex_init(&dev->msix_mutex); | ^~ include/linux/mutex.h:105:23: note: in definition of macro 'mutex_init' 105 | __mutex_init((mutex), #mutex, &__key); \ | ^~~~~ 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(a)lists.01.org [-- Attachment #2: config.gz --] [-- Type: application/gzip, Size: 34471 bytes --]
next reply other threads:[~2021-09-01 9:18 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-01 9:17 kernel test robot [this message] 2021-09-01 9:17 ` [meghadey-crypto:dmsix_new 3/10] drivers/pci/probe.c:2265:24: error: 'struct pci_dev' has no member named 'msix_mutex' 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=202109011740.Ui2f9smr-lkp@intel.com \ --to=lkp@intel.com \ --cc=kbuild-all@lists.01.org \ --cc=linux-kernel@vger.kernel.org \ --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: linkBe 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.