From: kernel test robot <lkp@intel.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org,
Alexandre Courbot <acourbot@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>
Subject: error[E0432]: unresolved import `kernel::firmware`
Date: Sat, 6 Dec 2025 17:26:56 +0800 [thread overview]
Message-ID: <202512061721.rxKGnt5q-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 416f99c3b16f582a3fc6d64a1f77f39d94b76de5
commit: 97ad568cd6a58804129ba071f3258b5c4782fb0d drm: nova: select NOVA_CORE
date: 5 weeks ago
config: x86_64-buildonly-randconfig-003-20251206 (https://download.01.org/0day-ci/archive/20251206/202512061721.rxKGnt5q-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/20251206/202512061721.rxKGnt5q-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/202512061721.rxKGnt5q-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0432]: unresolved import `kernel::firmware`
--> drivers/gpu/nova-core/firmware.rs:10:5
|
10 | use kernel::firmware;
| ^^^^^^^^^^^^^^^^ no `firmware` in the root
|
note: found an item that was configured out
--> rust/kernel/lib.rs:94:9
|
94 | pub mod firmware;
| ^^^^^^^^
note: the item is gated here
--> rust/kernel/lib.rs:93:1
|
93 | #[cfg(CONFIG_RUST_FW_LOADER_ABSTRACTIONS)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
help: consider importing this module instead
|
10 - use kernel::firmware;
10 + use crate::firmware;
|
--
>> error[E0432]: unresolved import `kernel::firmware`
--> drivers/gpu/nova-core/firmware/riscv.rs:9:13
|
9 | use kernel::firmware::Firmware;
| ^^^^^^^^ could not find `firmware` in `kernel`
|
note: found an item that was configured out
--> rust/kernel/lib.rs:94:9
|
94 | pub mod firmware;
| ^^^^^^^^
note: the item is gated here
--> rust/kernel/lib.rs:93:1
|
93 | #[cfg(CONFIG_RUST_FW_LOADER_ABSTRACTIONS)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
--
>> error[E0433]: failed to resolve: could not find `module_firmware` in `kernel`
--> drivers/gpu/nova-core/nova_core.rs:30:9
|
30 | kernel::module_firmware!(firmware::ModInfoBuilder);
| ^^^^^^^^^^^^^^^ could not find `module_firmware` in `kernel`
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for NOVA_CORE
Depends on [n]: HAS_IOMEM [=y] && 64BIT [=y] && PCI [=y] && RUST [=y] && RUST_FW_LOADER_ABSTRACTIONS [=n]
Selected by [y]:
- DRM_NOVA [=y] && HAS_IOMEM [=y] && 64BIT [=y] && DRM [=y]=y [=y] && PCI [=y] && RUST [=y]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-06 9:27 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=202512061721.rxKGnt5q-lkp@intel.com \
--to=lkp@intel.com \
--cc=acourbot@nvidia.com \
--cc=dakr@kernel.org \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--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