From: kernel test robot <lkp@intel.com>
To: Guixin Liu <kanie@linux.alibaba.com>
Cc: kbuild-all@lists.01.org, linux-nvme@lists.infradead.org,
Christoph Hellwig <hch@lst.de>
Subject: [linux-nvme:nvme-5.20 6/14] drivers/nvme/host/pci.c:3540:41: error: 'nvme_dev_pm_ops' undeclared here (not in a function); did you mean 'nvme_dev_map'?
Date: Thu, 21 Jul 2022 23:35:24 +0800 [thread overview]
Message-ID: <202207212326.SB1C57On-lkp@intel.com> (raw)
tree: git://git.infradead.org/nvme.git nvme-5.20
head: 750e34232a1152375907f28b6dd0262477a31f87
commit: 91d3073ff2f0b1a6a6d0629df7bcfacb226a204b [6/14] nvme-pci: use pm_sleep_ptr macro to declare nvme_dev_pm_ops
config: arm64-buildonly-randconfig-r001-20220721 (https://download.01.org/0day-ci/archive/20220721/202207212326.SB1C57On-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.1.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
git remote add linux-nvme git://git.infradead.org/nvme.git
git fetch --no-tags linux-nvme nvme-5.20
git checkout 91d3073ff2f0b1a6a6d0629df7bcfacb226a204b
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash drivers/nvme/host/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from include/linux/cpumask.h:10,
from include/linux/smp.h:13,
from include/linux/lockdep.h:14,
from include/linux/mutex.h:17,
from include/linux/kernfs.h:11,
from include/linux/sysfs.h:16,
from include/linux/kobject.h:20,
from include/linux/of.h:17,
from include/linux/irqdomain.h:35,
from include/linux/acpi.h:13,
from drivers/nvme/host/pci.c:7:
>> drivers/nvme/host/pci.c:3540:41: error: 'nvme_dev_pm_ops' undeclared here (not in a function); did you mean 'nvme_dev_map'?
3540 | .pm = pm_sleep_ptr(&nvme_dev_pm_ops),
| ^~~~~~~~~~~~~~~
include/linux/kernel.h:57:44: note: in definition of macro 'PTR_IF'
57 | #define PTR_IF(cond, ptr) ((cond) ? (ptr) : NULL)
| ^~~
drivers/nvme/host/pci.c:3540:27: note: in expansion of macro 'pm_sleep_ptr'
3540 | .pm = pm_sleep_ptr(&nvme_dev_pm_ops),
| ^~~~~~~~~~~~
vim +3540 drivers/nvme/host/pci.c
3532
3533 static struct pci_driver nvme_driver = {
3534 .name = "nvme",
3535 .id_table = nvme_id_table,
3536 .probe = nvme_probe,
3537 .remove = nvme_remove,
3538 .shutdown = nvme_shutdown,
3539 .driver = {
> 3540 .pm = pm_sleep_ptr(&nvme_dev_pm_ops),
3541 },
3542 .sriov_configure = pci_sriov_configure_simple,
3543 .err_handler = &nvme_err_handler,
3544 };
3545
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-07-21 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 15:35 kernel test robot [this message]
2022-07-21 15:38 ` [linux-nvme:nvme-5.20 6/14] drivers/nvme/host/pci.c:3540:41: error: 'nvme_dev_pm_ops' undeclared here (not in a function); did you mean 'nvme_dev_map'? Christoph Hellwig
2022-07-21 15:38 ` Christoph Hellwig
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=202207212326.SB1C57On-lkp@intel.com \
--to=lkp@intel.com \
--cc=hch@lst.de \
--cc=kanie@linux.alibaba.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-nvme@lists.infradead.org \
/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 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.