From: kernel test robot <lkp@intel.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, Daniel Gomez <da.gomez@samsung.com>
Subject: error[E0560]: struct `kunit_suite` has no field named `name`
Date: Fri, 21 Nov 2025 12:14:27 +0800 [thread overview]
Message-ID: <202511211258.1InbEyUs-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: fd95357fd8c6778ac7dea6c57a19b8b182b6e91f
commit: 818783c804bc051f7faf0ac226b5597f8259c6f8 module: make structure definitions always visible
date: 4 months ago
config: um-randconfig-001-20251121 (https://download.01.org/0day-ci/archive/20251121/202511211258.1InbEyUs-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 9e9fe08b16ea2c4d9867fb4974edf2a3776d6ece)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251121/202511211258.1InbEyUs-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/202511211258.1InbEyUs-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0560]: struct `kunit_suite` has no field named `name`
--> rust/kernel/kunit.rs:282:21
|
282 | name: KUNIT_TEST_SUITE_NAME,
| ^^^^ `kunit_suite` does not have this field
|
::: rust/kernel/alloc/kvec.rs:1244:1
|
1244 | #[macros::kunit_tests(rust_kvec_kunit)]
| --------------------------------------- in this procedural macro expansion
|
= note: all struct fields are already assigned
= note: this error originates in the macro `::kernel::kunit_unsafe_test_suite` which comes from the expansion of the attribute macro `macros::kunit_tests` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `kunit_suite` has no field named `test_cases`
--> rust/kernel/kunit.rs:287:21
|
287 | test_cases: unsafe {
| ^^^^^^^^^^ `kunit_suite` does not have this field
|
::: rust/kernel/alloc/kvec.rs:1244:1
|
1244 | #[macros::kunit_tests(rust_kvec_kunit)]
| --------------------------------------- in this procedural macro expansion
|
= note: all struct fields are already assigned
= note: this error originates in the macro `::kernel::kunit_unsafe_test_suite` which comes from the expansion of the attribute macro `macros::kunit_tests` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `kunit_suite` has no field named `suite_init`
--> rust/kernel/kunit.rs:291:21
|
291 | suite_init: None,
| ^^^^^^^^^^ `kunit_suite` does not have this field
|
::: rust/kernel/alloc/kvec.rs:1244:1
|
1244 | #[macros::kunit_tests(rust_kvec_kunit)]
| --------------------------------------- in this procedural macro expansion
|
= note: all struct fields are already assigned
= note: this error originates in the macro `::kernel::kunit_unsafe_test_suite` which comes from the expansion of the attribute macro `macros::kunit_tests` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `kunit_suite` has no field named `suite_exit`
--> rust/kernel/kunit.rs:292:21
|
292 | suite_exit: None,
| ^^^^^^^^^^ `kunit_suite` does not have this field
|
::: rust/kernel/alloc/kvec.rs:1244:1
|
1244 | #[macros::kunit_tests(rust_kvec_kunit)]
| --------------------------------------- in this procedural macro expansion
|
= note: all struct fields are already assigned
= note: this error originates in the macro `::kernel::kunit_unsafe_test_suite` which comes from the expansion of the attribute macro `macros::kunit_tests` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `kunit_suite` has no field named `init`
--> rust/kernel/kunit.rs:293:21
|
293 | init: None,
| ^^^^ `kunit_suite` does not have this field
|
::: rust/kernel/alloc/kvec.rs:1244:1
|
1244 | #[macros::kunit_tests(rust_kvec_kunit)]
| --------------------------------------- in this procedural macro expansion
|
= note: all struct fields are already assigned
= note: this error originates in the macro `::kernel::kunit_unsafe_test_suite` which comes from the expansion of the attribute macro `macros::kunit_tests` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `kunit_suite` has no field named `exit`
--> rust/kernel/kunit.rs:294:21
|
294 | exit: None,
| ^^^^ `kunit_suite` does not have this field
|
::: rust/kernel/alloc/kvec.rs:1244:1
|
1244 | #[macros::kunit_tests(rust_kvec_kunit)]
| --------------------------------------- in this procedural macro expansion
|
= note: all struct fields are already assigned
= note: this error originates in the macro `::kernel::kunit_unsafe_test_suite` which comes from the expansion of the attribute macro `macros::kunit_tests` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `kunit_suite` has no field named `attr`
--> rust/kernel/kunit.rs:295:21
|
295 | attr: ::kernel::bindings::kunit_attributes {
| ^^^^ `kunit_suite` does not have this field
|
::: rust/kernel/alloc/kvec.rs:1244:1
|
1244 | #[macros::kunit_tests(rust_kvec_kunit)]
| --------------------------------------- in this procedural macro expansion
|
= note: all struct fields are already assigned
= note: this error originates in the macro `::kernel::kunit_unsafe_test_suite` which comes from the expansion of the attribute macro `macros::kunit_tests` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `kunit_suite` has no field named `status_comment`
--> rust/kernel/kunit.rs:298:21
|
298 | status_comment: [0; 256usize],
| ^^^^^^^^^^^^^^ `kunit_suite` does not have this field
|
::: rust/kernel/alloc/kvec.rs:1244:1
|
1244 | #[macros::kunit_tests(rust_kvec_kunit)]
| --------------------------------------- in this procedural macro expansion
|
= note: all struct fields are already assigned
= note: this error originates in the macro `::kernel::kunit_unsafe_test_suite` which comes from the expansion of the attribute macro `macros::kunit_tests` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `kunit_suite` has no field named `debugfs`
--> rust/kernel/kunit.rs:299:21
|
299 | debugfs: ::core::ptr::null_mut(),
| ^^^^^^^ `kunit_suite` does not have this field
|
::: rust/kernel/alloc/kvec.rs:1244:1
|
1244 | #[macros::kunit_tests(rust_kvec_kunit)]
| --------------------------------------- in this procedural macro expansion
|
= note: all struct fields are already assigned
= note: this error originates in the macro `::kernel::kunit_unsafe_test_suite` which comes from the expansion of the attribute macro `macros::kunit_tests` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `kunit_suite` has no field named `log`
--> rust/kernel/kunit.rs:300:21
|
300 | log: ::core::ptr::null_mut(),
| ^^^ `kunit_suite` does not have this field
|
::: rust/kernel/alloc/kvec.rs:1244:1
|
1244 | #[macros::kunit_tests(rust_kvec_kunit)]
| --------------------------------------- in this procedural macro expansion
|
= note: all struct fields are already assigned
= note: this error originates in the macro `::kernel::kunit_unsafe_test_suite` which comes from the expansion of the attribute macro `macros::kunit_tests` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `kunit_suite` has no field named `suite_init_err`
--> rust/kernel/kunit.rs:301:21
|
301 | suite_init_err: 0,
| ^^^^^^^^^^^^^^ `kunit_suite` does not have this field
|
::: rust/kernel/alloc/kvec.rs:1244:1
|
1244 | #[macros::kunit_tests(rust_kvec_kunit)]
| --------------------------------------- in this procedural macro expansion
|
= note: all struct fields are already assigned
= note: this error originates in the macro `::kernel::kunit_unsafe_test_suite` which comes from the expansion of the attribute macro `macros::kunit_tests` (in Nightly builds, run with -Z macro-backtrace for more info)
..
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-21 4:15 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=202511211258.1InbEyUs-lkp@intel.com \
--to=lkp@intel.com \
--cc=da.gomez@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=thomas.weissschuh@linutronix.de \
/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.