From: kernel test robot <lkp@intel.com>
To: Keith Busch <keith.busch@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, Rajat Jain <rajatja@google.com>,
Gwendal Grignou <gwendal@chromium.org>
Subject: [jsarha:topic/chromeos-4.19-s0ix 7573/9999] drivers/nvme/host/pci.c:2705:25: sparse: sparse: symbol 'nvme_dev_pm_ops' was not declared. Should it be static?
Date: Sat, 4 Feb 2023 18:49:06 +0800 [thread overview]
Message-ID: <202302041816.01TYjFuu-lkp@intel.com> (raw)
tree: https://github.com/jsarha/linux topic/chromeos-4.19-s0ix
head: 430bdaa0a8c38697780f45a148964d71951df11f
commit: bc7304877066a781782a7b43ea0ed2edcc767637 [7573/9999] BACKPORT: FROMGIT: nvme-pci: Use host managed power state for suspend
config: i386-randconfig-s002 (https://download.01.org/0day-ci/archive/20230204/202302041816.01TYjFuu-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-39-gce1a6720-dirty
# https://github.com/jsarha/linux/commit/bc7304877066a781782a7b43ea0ed2edcc767637
git remote add jsarha https://github.com/jsarha/linux
git fetch --no-tags jsarha topic/chromeos-4.19-s0ix
git checkout bc7304877066a781782a7b43ea0ed2edcc767637
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 olddefconfig
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 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>
sparse warnings: (new ones prefixed by >>)
>> drivers/nvme/host/pci.c:2705:25: sparse: sparse: symbol 'nvme_dev_pm_ops' was not declared. Should it be static?
drivers/nvme/host/pci.c:1263: warning: Function parameter or member 'nvmeq' not described in 'nvme_suspend_queue'
vim +/nvme_dev_pm_ops +2705 drivers/nvme/host/pci.c
2704
> 2705 const struct dev_pm_ops nvme_dev_pm_ops = {
2706 .suspend = nvme_suspend,
2707 .resume = nvme_resume,
2708 .freeze = nvme_simple_suspend,
2709 .thaw = nvme_simple_resume,
2710 .poweroff = nvme_simple_suspend,
2711 .restore = nvme_simple_resume,
2712 };
2713
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next reply other threads:[~2023-02-04 10:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 10:49 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-19 1:02 [jsarha:topic/chromeos-4.19-s0ix 7573/9999] drivers/nvme/host/pci.c:2705:25: sparse: sparse: symbol 'nvme_dev_pm_ops' was not declared. Should it be static? kernel test robot
2022-04-11 19:25 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=202302041816.01TYjFuu-lkp@intel.com \
--to=lkp@intel.com \
--cc=gwendal@chromium.org \
--cc=keith.busch@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rajatja@google.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 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.