All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
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: Fri, 19 Apr 2024 09:02:05 +0800	[thread overview]
Message-ID: <202404190855.Bmsj8VGO-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: x86_64-randconfig-123-20240419 (https://download.01.org/0day-ci/archive/20240419/202404190855.Bmsj8VGO-lkp@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240419/202404190855.Bmsj8VGO-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202404190855.Bmsj8VGO-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'
   drivers/nvme/host/pci.o: warning: objtool: __nvme_alloc_host_mem()+0x90: sibling call from callable instruction with modified stack frame
   drivers/nvme/host/pci.o: warning: objtool: nvme_pci_cmd_size()+0x63: sibling call from callable instruction with modified stack frame
   drivers/nvme/host/pci.o: warning: objtool: nvme_pci_setup_prps()+0x211: sibling call from callable instruction with modified stack frame
   drivers/nvme/host/pci.o: warning: objtool: nvme_set_host_mem()+0x107: sibling call from callable instruction with modified stack frame
   drivers/nvme/host/pci.o: warning: objtool: nvme_alloc_sq_cmds()+0xa1: sibling call from callable instruction with modified stack frame
   drivers/nvme/host/pci.o: warning: objtool: nvme_free_iod()+0x1e9: sibling call from callable instruction with modified stack frame
   drivers/nvme/host/pci.o: warning: objtool: nvme_map_data()+0x2d1: sibling call from callable instruction with modified stack frame
   drivers/nvme/host/pci.o: warning: objtool: nvme_timeout()+0x1b5: sibling call from callable instruction with modified stack frame
   drivers/nvme/host/pci.o: warning: objtool: nvme_map_cmb()+0x14f: sibling call from callable instruction with modified stack frame
   drivers/nvme/host/pci.o: warning: objtool: nvme_create_queue()+0xbe: sibling call from callable instruction with modified stack frame
   drivers/nvme/host/pci.o: warning: objtool: nvme_setup_io_queues()+0x63d: sibling call from callable instruction with modified stack frame

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/wiki

             reply	other threads:[~2024-04-19  1:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19  1:02 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-04 10:49 [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=202404190855.Bmsj8VGO-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@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 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.