From: kernel test robot <lkp@intel.com>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Jens Axboe <axboe@kernel.dk>, Anuj Gupta <anuj20.g@samsung.com>
Subject: [axboe:nvme-raw-queues 6/16] drivers/nvme/host/pci.c:2421:3: error: field designator 'register_queue' does not refer to any field in type 'const struct blk_mq_ops'
Date: Thu, 07 May 2026 00:46:43 +0800 [thread overview]
Message-ID: <202605070041.kByaHcMe-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git nvme-raw-queues
head: 38cfa7887dc8d403af2baa576d06c438408a192c
commit: 6c88c997f65b7435f11d31654c1d5007c6f82335 [6/16] pci: implement register/unregister functionality
config: loongarch-randconfig-001 (https://download.01.org/0day-ci/archive/20260507/202605070041.kByaHcMe-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260507/202605070041.kByaHcMe-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/202605070041.kByaHcMe-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/nvme/host/pci.c:2421:3: error: field designator 'register_queue' does not refer to any field in type 'const struct blk_mq_ops'
2421 | .register_queue = nvme_pci_register_queue,
| ~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/nvme/host/pci.c:2422:3: error: field designator 'unregister_queue' does not refer to any field in type 'const struct blk_mq_ops'
2422 | .unregister_queue = nvme_pci_unregister_queue,
| ~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2 errors generated.
vim +2421 drivers/nvme/host/pci.c
2410
2411 static const struct blk_mq_ops nvme_mq_ops = {
2412 .queue_rq = nvme_queue_rq,
2413 .queue_rqs = nvme_queue_rqs,
2414 .complete = nvme_pci_complete_rq,
2415 .commit_rqs = nvme_commit_rqs,
2416 .init_hctx = nvme_init_hctx,
2417 .init_request = nvme_pci_init_request,
2418 .map_queues = nvme_pci_map_queues,
2419 .timeout = nvme_timeout,
2420 .poll = nvme_poll,
> 2421 .register_queue = nvme_pci_register_queue,
> 2422 .unregister_queue = nvme_pci_unregister_queue,
2423 };
2424
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-06 16: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=202605070041.kByaHcMe-lkp@intel.com \
--to=lkp@intel.com \
--cc=anuj20.g@samsung.com \
--cc=axboe@kernel.dk \
--cc=joshi.k@samsung.com \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox