llvm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Andreas Hindborg <a.hindborg@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Daniel Gomez <da.gomez@kernel.org>,
	Benno Lossin <lossin@kernel.org>
Subject: [linux-next:master 4806/10599] error[E0560]: struct `bindings::kernel_param_ops` has no field named `get`
Date: Fri, 21 Nov 2025 08:24:02 +0800	[thread overview]
Message-ID: <202511210858.uwVivgvn-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   88cbd8ac379cf5ce68b7efcfd4d1484a6871ee0b
commit: 0b08fc292842a13aa496413b48c1efb83573b8c6 [4806/10599] rust: introduce module_param module
config: um-randconfig-001-20251121 (https://download.01.org/0day-ci/archive/20251121/202511210858.uwVivgvn-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/202511210858.uwVivgvn-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/202511210858.uwVivgvn-lkp@intel.com/

All errors (new ones prefixed by >>):

>> error[E0560]: struct `bindings::kernel_param_ops` has no field named `get`
   --> rust/kernel/module_param.rs:166:13
   |
   166 |             get: None,
   |             ^^^ `bindings::kernel_param_ops` does not have this field
   ...
   177 | make_param_ops!(PARAM_OPS_U32, u32);
   | ----------------------------------- in this macro invocation
   |
   = note: all struct fields are already assigned
   = note: this error originates in the macro `make_param_ops` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `bindings::kernel_param_ops` has no field named `free`
   --> rust/kernel/module_param.rs:167:13
   |
   167 |             free: None,
   |             ^^^^ `bindings::kernel_param_ops` does not have this field
   ...
   177 | make_param_ops!(PARAM_OPS_U32, u32);
   | ----------------------------------- in this macro invocation
   |
   = note: all struct fields are already assigned
   = note: this error originates in the macro `make_param_ops` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `bindings::kernel_param_ops` has no field named `flags`
   --> rust/kernel/module_param.rs:164:13
   |
   164 |             flags: 0,
   |             ^^^^^ `bindings::kernel_param_ops` does not have this field
   ...
   178 | make_param_ops!(PARAM_OPS_I64, i64);
   | ----------------------------------- in this macro invocation
   |
   = note: all struct fields are already assigned
   = note: this error originates in the macro `make_param_ops` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `bindings::kernel_param_ops` has no field named `set`
   --> rust/kernel/module_param.rs:165:13
   |
   165 |             set: Some(set_param::<$ty>),
   |             ^^^ `bindings::kernel_param_ops` does not have this field
   ...
   178 | make_param_ops!(PARAM_OPS_I64, i64);
   | ----------------------------------- in this macro invocation
   |
   = note: all struct fields are already assigned
   = note: this error originates in the macro `make_param_ops` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `bindings::kernel_param_ops` has no field named `get`
   --> rust/kernel/module_param.rs:166:13
   |
   166 |             get: None,
   |             ^^^ `bindings::kernel_param_ops` does not have this field
   ...
   178 | make_param_ops!(PARAM_OPS_I64, i64);
   | ----------------------------------- in this macro invocation
   |
   = note: all struct fields are already assigned
   = note: this error originates in the macro `make_param_ops` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `bindings::kernel_param_ops` has no field named `free`
   --> rust/kernel/module_param.rs:167:13
   |
   167 |             free: None,
   |             ^^^^ `bindings::kernel_param_ops` does not have this field
   ...
   178 | make_param_ops!(PARAM_OPS_I64, i64);
   | ----------------------------------- in this macro invocation
   |
   = note: all struct fields are already assigned
   = note: this error originates in the macro `make_param_ops` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `bindings::kernel_param_ops` has no field named `flags`
   --> rust/kernel/module_param.rs:164:13
   |
   164 |             flags: 0,
   |             ^^^^^ `bindings::kernel_param_ops` does not have this field
   ...
   179 | make_param_ops!(PARAM_OPS_U64, u64);
   | ----------------------------------- in this macro invocation
   |
   = note: all struct fields are already assigned
   = note: this error originates in the macro `make_param_ops` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `bindings::kernel_param_ops` has no field named `set`
   --> rust/kernel/module_param.rs:165:13
   |
   165 |             set: Some(set_param::<$ty>),
   |             ^^^ `bindings::kernel_param_ops` does not have this field
   ...
   179 | make_param_ops!(PARAM_OPS_U64, u64);
   | ----------------------------------- in this macro invocation
   |
   = note: all struct fields are already assigned
   = note: this error originates in the macro `make_param_ops` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `bindings::kernel_param_ops` has no field named `get`
   --> rust/kernel/module_param.rs:166:13
   |
   166 |             get: None,
   |             ^^^ `bindings::kernel_param_ops` does not have this field
   ...
   179 | make_param_ops!(PARAM_OPS_U64, u64);
   | ----------------------------------- in this macro invocation
   |
   = note: all struct fields are already assigned
   = note: this error originates in the macro `make_param_ops` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `bindings::kernel_param_ops` has no field named `free`
   --> rust/kernel/module_param.rs:167:13
   |
   167 |             free: None,
   |             ^^^^ `bindings::kernel_param_ops` does not have this field
   ...
   179 | make_param_ops!(PARAM_OPS_U64, u64);
   | ----------------------------------- in this macro invocation
   |
   = note: all struct fields are already assigned
   = note: this error originates in the macro `make_param_ops` (in Nightly builds, run with -Z macro-backtrace for more info)
--
>> error[E0560]: struct `bindings::kernel_param_ops` has no field named `flags`
   --> rust/kernel/module_param.rs:164:13
   |
   164 |             flags: 0,
   |             ^^^^^ `bindings::kernel_param_ops` does not have this field
   ...
   180 | make_param_ops!(PARAM_OPS_ISIZE, isize);
   | --------------------------------------- in this macro invocation
   |
   = note: all struct fields are already assigned
   = note: this error originates in the macro `make_param_ops` (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  0:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21  0:24 kernel test robot [this message]
2025-11-26 13:41 ` [linux-next:master 4806/10599] error[E0560]: struct `bindings::kernel_param_ops` has no field named `get` Daniel Gomez
2025-11-26 13:50   ` Miguel Ojeda
2025-11-27  9:26     ` David Gow

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=202511210858.uwVivgvn-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=a.hindborg@kernel.org \
    --cc=da.gomez@kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=lossin@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).