From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [asahilinux:nvme/dev 1/9] drivers/nvme/host/pci.c:1422: warning: expecting prototype for nvme_pci_suspend_queue(). Prototype was for nvme_suspend_queue() instead
Date: Wed, 09 Jun 2021 01:47:43 +0800 [thread overview]
Message-ID: <202106090130.v9lWL54o-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3638 bytes --]
tree: https://github.com/AsahiLinux/linux nvme/dev
head: 69142df77238252d5ab52d940bcff054c4dcd551
commit: 4a80db096ae7aa82737bec490021db9523d2355d [1/9] nvme: pci: rename pci specific functions
config: i386-randconfig-a011-20210608 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/AsahiLinux/linux/commit/4a80db096ae7aa82737bec490021db9523d2355d
git remote add asahilinux https://github.com/AsahiLinux/linux
git fetch --no-tags asahilinux nvme/dev
git checkout 4a80db096ae7aa82737bec490021db9523d2355d
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/nvme/host/pci.c:1422: warning: expecting prototype for nvme_pci_suspend_queue(). Prototype was for nvme_suspend_queue() instead
vim +1422 drivers/nvme/host/pci.c
4a80db096ae7aa drivers/nvme/host/pci.c Arnd Bergmann 2021-02-11 1415
4a80db096ae7aa drivers/nvme/host/pci.c Arnd Bergmann 2021-02-11 1416
4d115420707afc drivers/block/nvme-core.c Keith Busch 2013-12-10 1417 /**
4a80db096ae7aa drivers/nvme/host/pci.c Arnd Bergmann 2021-02-11 1418 * nvme_pci_suspend_queue - put queue into suspended state
40581d1a91a152 drivers/nvme/host/pci.c Bart Van Assche 2018-10-08 1419 * @nvmeq: queue to suspend
4d115420707afc drivers/block/nvme-core.c Keith Busch 2013-12-10 1420 */
4d115420707afc drivers/block/nvme-core.c Keith Busch 2013-12-10 1421 static int nvme_suspend_queue(struct nvme_queue *nvmeq)
b60503ba432b16 drivers/block/nvme.c Matthew Wilcox 2011-01-20 @1422 {
4e224106673f1e drivers/nvme/host/pci.c Christoph Hellwig 2018-12-02 1423 if (!test_and_clear_bit(NVMEQ_ENABLED, &nvmeq->flags))
2b25d981790b83 drivers/block/nvme-core.c Keith Busch 2014-12-22 1424 return 1;
a09115b23e2002 drivers/block/nvme.c Matthew Wilcox 2012-08-07 1425
4e224106673f1e drivers/nvme/host/pci.c Christoph Hellwig 2018-12-02 1426 /* ensure that nvme_queue_rq() sees NVMEQ_ENABLED cleared */
d1f06f4ae0410f drivers/nvme/host/pci.c Jens Axboe 2018-05-17 1427 mb();
a09115b23e2002 drivers/block/nvme.c Matthew Wilcox 2012-08-07 1428
4e224106673f1e drivers/nvme/host/pci.c Christoph Hellwig 2018-12-02 1429 nvmeq->dev->online_queues--;
1c63dc66580d4b drivers/nvme/host/pci.c Christoph Hellwig 2015-11-26 1430 if (!nvmeq->qid && nvmeq->dev->ctrl.admin_q)
c81545f991a661 drivers/nvme/host/pci.c Sagi Grimberg 2017-07-02 1431 blk_mq_quiesce_queue(nvmeq->dev->ctrl.admin_q);
7c349dde26b75d drivers/nvme/host/pci.c Keith Busch 2019-03-08 1432 if (!test_and_clear_bit(NVMEQ_POLLED, &nvmeq->flags))
4a80db096ae7aa drivers/nvme/host/pci.c Arnd Bergmann 2021-02-11 1433 nvme_queue_free_irq(nvmeq);
4d115420707afc drivers/block/nvme-core.c Keith Busch 2013-12-10 1434 return 0;
b60503ba432b16 drivers/block/nvme.c Matthew Wilcox 2011-01-20 1435 }
b60503ba432b16 drivers/block/nvme.c Matthew Wilcox 2011-01-20 1436
:::::: The code at line 1422 was first introduced by commit
:::::: b60503ba432b16fc84442a84e29a7aad2c0c363d NVMe: New driver
:::::: TO: Matthew Wilcox <matthew.r.wilcox@intel.com>
:::::: CC: Matthew Wilcox <matthew.r.wilcox@intel.com>
---
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: 42117 bytes --]
reply other threads:[~2021-06-08 17:47 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=202106090130.v9lWL54o-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.