From: kernel test robot <lkp@intel.com>
To: Manos Pitsidianakis <manos@pitsidianak.is>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>
Subject: warning: unresolved link to `virtio_device_table`
Date: Wed, 13 May 2026 14:37:48 +0200 [thread overview]
Message-ID: <202605131459.OWBsBSFi-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Manos-Pitsidianakis/rust-bindings-generate-virtio-bindings/20260513-065912
head: dcbb217532e1f25cb932bf8b1019d1085373a6df
commit: a64ae4106bf2576331e81e44d512d4739796067d rust: add virtio module
date: 14 hours ago
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260513/202605131459.OWBsBSFi-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260513/202605131459.OWBsBSFi-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/202605131459.OWBsBSFi-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> warning: unresolved link to `virtio_device_table`
--> rust/kernel/virtio.rs:7:66
|
7 | //! - Implement the [`Driver`] trait for your driver type (use [`virtio_device_table`] macro to
| ^^^^^^^^^^^^^^^^^^^ no item named `virtio_device_table` in scope
|
= note: `macro_rules` named `virtio_device_table` exists in this crate, but it is not in scope at this link's location
= note: `#[warn(rustdoc::broken_intra_doc_links)]` on by default
--
>> warning: unresolved link to `module_virtio_driver`
--> rust/kernel/virtio.rs:9:17
|
9 | //! - Use the [`module_virtio_driver`] macro to declare your module
| ^^^^^^^^^^^^^^^^^^^^ no item named `module_virtio_driver` in scope
|
= note: `macro_rules` named `module_virtio_driver` exists in this crate, but it is not in scope at this link's location
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-13 12:38 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=202605131459.OWBsBSFi-lkp@intel.com \
--to=lkp@intel.com \
--cc=manos@pitsidianak.is \
--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.