From: kernel test robot <lkp@intel.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Alice Ryhl <aliceryhl@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [linux-next:master 4075/10599] error[E0609]: no field `p` on type `bindings::device`
Date: Fri, 21 Nov 2025 12:14:35 +0800 [thread overview]
Message-ID: <202511211216.EUD1BISe-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 88cbd8ac379cf5ce68b7efcfd4d1484a6871ee0b
commit: 6f61a2637abe4f89877da3280775565baedb60e0 [4075/10599] rust: device: introduce Device::drvdata()
config: um-randconfig-001-20251121 (https://download.01.org/0day-ci/archive/20251121/202511211216.EUD1BISe-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/202511211216.EUD1BISe-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/202511211216.EUD1BISe-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0609]: no field `p` on type `bindings::device`
--> rust/kernel/device.rs:206:49
|
206 | let private = unsafe { (*self.as_raw()).p };
| ^ unknown field
|
= note: available field is: `_address`
--
>> error[E0609]: no field `p` on type `bindings::device`
--> rust/kernel/device.rs:291:49
|
291 | let private = unsafe { (*self.as_raw()).p };
| ^ unknown field
|
= note: available field is: `_address`
--
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=202511211216.EUD1BISe-lkp@intel.com \
--to=lkp@intel.com \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.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 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.