From: kernel test robot <lkp@intel.com>
To: Aaron Tomlin <atomlin@atomlin.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 6196/6545] error[E0425]: cannot find type `initcall_modname` in crate `::kernel::bindings`
Date: Sun, 20 Sep 2026 14:22:08 +0800 [thread overview]
Message-ID: <202609201402.NyS4lCWY-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 3f2425f5b5bbbdd991ca9cdfd5502e68d8895998
commit: b83e83203582477b2ad0631e29e6fd88295cd9b1 [6196/6545] module: extend module_blacklist parameter to built-in modules
config: x86_64-randconfig-1010-20260919 (https://download.01.org/0day-ci/archive/20260920/202609201402.NyS4lCWY-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260920/202609201402.NyS4lCWY-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/202609201402.NyS4lCWY-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0425]: cannot find type `initcall_modname` in crate `::kernel::bindings`
--> rust/doctests_kernel_generated.rs:7459:1
|
7459 | / module! {
7460 | | type: MyModule,
7461 | | name: "module_firmware_test",
7462 | | authors: ["Rust for Linux"],
7463 | | description: "module_firmware! test module",
7464 | | license: "GPL",
7465 | | }
| |_^ not found in `::kernel::bindings`
|
= note: this error originates in the macro `module` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0422]: cannot find struct, variant or union type `initcall_modname` in crate `::kernel::bindings`
--> rust/doctests_kernel_generated.rs:7459:1
|
7459 | / module! {
7460 | | type: MyModule,
7461 | | name: "module_firmware_test",
7462 | | authors: ["Rust for Linux"],
7463 | | description: "module_firmware! test module",
7464 | | license: "GPL",
7465 | | }
| |_^ not found in `::kernel::bindings`
|
= note: this error originates in the macro `module` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0425]: cannot find type `initcall_modname` in crate `::kernel::bindings`
--> rust/doctests_kernel_generated.rs:12639:1
|
12639 | / kernel::module_phy_driver! {
12640 | | drivers: [PhySample],
12641 | | device_table: [
12642 | | DeviceId::new_with_driver::<PhySample>()
... |
12647 | | license: "GPL",
12648 | | }
| |_^ not found in `::kernel::bindings`
|
= note: this error originates in the macro `$crate::prelude::module` which comes from the expansion of the macro `kernel::module_phy_driver` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0422]: cannot find struct, variant or union type `initcall_modname` in crate `::kernel::bindings`
--> rust/doctests_kernel_generated.rs:12639:1
|
12639 | / kernel::module_phy_driver! {
12640 | | drivers: [PhySample],
12641 | | device_table: [
12642 | | DeviceId::new_with_driver::<PhySample>()
... |
12647 | | license: "GPL",
12648 | | }
| |_^ not found in `::kernel::bindings`
|
= note: this error originates in the macro `$crate::prelude::module` which comes from the expansion of the macro `kernel::module_phy_driver` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0425]: cannot find type `initcall_modname` in crate `::kernel::bindings`
--> samples/rust/rust_driver_serdev.rs:82:1
|
82 | / kernel::module_serdev_device_driver! {
83 | | type: SampleDriver,
84 | | name: "rust_driver_serdev",
85 | | authors: ["Markus Probst"],
86 | | description: "Rust Serial device bus device driver",
87 | | license: "GPL v2",
88 | | }
| |_^ not found in `::kernel::bindings`
|
= note: this error originates in the macro `$crate::prelude::module` which comes from the expansion of the macro `kernel::module_serdev_device_driver` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0422]: cannot find struct, variant or union type `initcall_modname` in crate `::kernel::bindings`
--> samples/rust/rust_driver_serdev.rs:82:1
|
82 | / kernel::module_serdev_device_driver! {
83 | | type: SampleDriver,
84 | | name: "rust_driver_serdev",
85 | | authors: ["Markus Probst"],
86 | | description: "Rust Serial device bus device driver",
87 | | license: "GPL v2",
88 | | }
| |_^ not found in `::kernel::bindings`
|
= note: this error originates in the macro `$crate::prelude::module` which comes from the expansion of the macro `kernel::module_serdev_device_driver` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0425]: cannot find type `initcall_modname` in crate `::kernel::bindings`
--> samples/rust/rust_driver_faux.rs:11:1
|
11 | / module! {
12 | | type: SampleModule,
13 | | name: "rust_faux_driver",
14 | | authors: ["Lyude Paul"],
15 | | description: "Rust faux device sample",
16 | | license: "GPL",
17 | | }
| |_^ not found in `::kernel::bindings`
|
= note: this error originates in the macro `module` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0422]: cannot find struct, variant or union type `initcall_modname` in crate `::kernel::bindings`
--> samples/rust/rust_driver_faux.rs:11:1
|
11 | / module! {
12 | | type: SampleModule,
13 | | name: "rust_faux_driver",
14 | | authors: ["Lyude Paul"],
15 | | description: "Rust faux device sample",
16 | | license: "GPL",
17 | | }
| |_^ not found in `::kernel::bindings`
|
= note: this error originates in the macro `module` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0425]: cannot find type `initcall_modname` in crate `::kernel::bindings`
--> samples/rust/rust_debugfs_scoped.rs:24:1
|
24 | / module! {
25 | | type: RustScopedDebugFs,
26 | | name: "rust_debugfs_scoped",
27 | | authors: ["Matthew Maurer"],
28 | | description: "Rust Scoped DebugFS usage sample",
29 | | license: "GPL",
30 | | }
| |_^ not found in `::kernel::bindings`
|
= note: this error originates in the macro `module` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0422]: cannot find struct, variant or union type `initcall_modname` in crate `::kernel::bindings`
--> samples/rust/rust_debugfs_scoped.rs:24:1
|
24 | / module! {
25 | | type: RustScopedDebugFs,
26 | | name: "rust_debugfs_scoped",
27 | | authors: ["Matthew Maurer"],
28 | | description: "Rust Scoped DebugFS usage sample",
29 | | license: "GPL",
30 | | }
| |_^ not found in `::kernel::bindings`
|
= note: this error originates in the macro `module` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0425]: cannot find type `initcall_modname` in crate `::kernel::bindings`
--> samples/rust/rust_dma.rs:136:1
|
136 | / kernel::module_pci_driver! {
137 | | type: DmaSampleDriver,
138 | | name: "rust_dma",
139 | | authors: ["Abdiel Janulgue"],
140 | | description: "Rust DMA test",
141 | | license: "GPL v2",
142 | | }
| |_^ not found in `::kernel::bindings`
|
= note: this error originates in the macro `$crate::prelude::module` which comes from the expansion of the macro `kernel::module_pci_driver` (in Nightly builds, run with -Z macro-backtrace for more info)
..
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-09-20 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 6:22 kernel test robot [this message]
2026-09-25 17:06 ` [linux-next:master 6196/6545] error[E0425]: cannot find type `initcall_modname` in crate `::kernel::bindings` Aaron Tomlin
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=202609201402.NyS4lCWY-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=atomlin@atomlin.com \
--cc=linux-mm@kvack.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