[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <202502162042.nKMk0Rff-lkp@intel.com>
Date: Sun, 16 Feb 2025 20:35:59 +0800
From: kernel test robot <lkp@...el.com>
To: Guilherme Giacomo Simoes <trintaeoitogc@...il.com>,
a.hindborg@...nel.org, alex.gaynor@...il.com, aliceryhl@...gle.com,
apw@...onical.com, arnd@...db.de, aswinunni01@...il.com,
axboe@...nel.dk, benno.lossin@...ton.me, bhelgaas@...gle.com,
bjorn3_gh@...tonmail.com, boqun.feng@...il.com, dakr@...nel.org,
dwaipayanray1@...il.com, ethan.twardy@...il.com,
fujita.tomonori@...il.com, gary@...yguo.net,
gregkh@...uxfoundation.org, joe@...ches.com,
lukas.bulwahn@...il.com, ojeda@...nel.org, pbonzini@...hat.com,
tmgross@...ch.edu, walmeida@...rosoft.com
Cc: llvm@...ts.linux.dev, oe-kbuild-all@...ts.linux.dev,
trintaeoitogc@...il.com, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org,
Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Subject: Re: [PATCH V2 1/2] rust: module: change author to be a array
Hi Guilherme,
kernel test robot noticed the following build errors:
[auto build test ERROR on rust/rust-next]
[also build test ERROR on pci/next pci/for-linus char-misc/char-misc-testing char-misc/char-misc-next char-misc/char-misc-linus linus/master v6.14-rc2 next-20250214]
[cannot apply to rust/rust-block-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Guilherme-Giacomo-Simoes/rust-module-change-author-to-be-a-array/20250215-024906
base: https://github.com/Rust-for-Linux/linux rust-next
patch link: https://lore.kernel.org/r/20250214184550.120775-2-trintaeoitogc%40gmail.com
patch subject: [PATCH V2 1/2] rust: module: change author to be a array
config: x86_64-randconfig-006-20250216 (https://download.01.org/0day-ci/archive/20250216/202502162042.nKMk0Rff-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250216/202502162042.nKMk0Rff-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@...el.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202502162042.nKMk0Rff-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error: proc macro panicked
--> samples/rust/rust_driver_platform.rs:43:1
|
43 | / kernel::module_platform_driver! {
44 | | type: SampleDriver,
45 | | name: "rust_driver_platform",
46 | | author: "Danilo Krummrich",
47 | | description: "Rust Platform driver",
48 | | license: "GPL v2",
49 | | }
| |_^
|
= help: message: Expected Group
= note: this error originates in the macro `$crate::module_driver` which comes from the expansion of the macro `kernel::module_platform_driver` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0277]: the trait bound `DriverModule: ModuleMetadata` is not satisfied
--> samples/rust/rust_driver_platform.rs:43:1
|
43 | / kernel::module_platform_driver! {
44 | | type: SampleDriver,
45 | | name: "rust_driver_platform",
46 | | author: "Danilo Krummrich",
47 | | description: "Rust Platform driver",
48 | | license: "GPL v2",
49 | | }
| |_^ the trait `ModuleMetadata` is not implemented for `DriverModule`
|
= note: this error originates in the macro `$crate::module_driver` which comes from the expansion of the macro `kernel::module_platform_driver` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error: proc macro panicked
--> drivers/net/phy/ax88796b_rust.rs:14:1
|
14 | / kernel::module_phy_driver! {
15 | | drivers: [PhyAX88772A, PhyAX88772C, PhyAX88796B],
16 | | device_table: [
17 | | DeviceId::new_with_driver::<PhyAX88772A>(),
... |
24 | | license: "GPL",
25 | | }
| |_^
|
= help: message: Expected Group
= note: this error originates in the macro `kernel::module_phy_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
Powered by blists - more mailing lists