From: kernel test robot <lkp@intel.com>
To: Igor Korotin <igor.korotin.linux@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Danilo Krummrich <dakr@kernel.org>
Subject: [linux-next:master 8985/13171] error[E0609]: no field `id_table` on type `i2c_driver`
Date: Tue, 2 Dec 2025 07:50:48 +0800 [thread overview]
Message-ID: <202512020708.C7Q0UXB2-lkp@intel.com> (raw)
Hi Igor,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 95cb2fd6ce0ad61af54191fe5ef271d7177f9c3a
commit: 57c5bd9aee944b0f5c2ab314e10a86fae51f7bf2 [8985/13171] rust: i2c: add basic I2C device and driver abstractions
config: arm64-randconfig-001-20251202 (https://download.01.org/0day-ci/archive/20251202/202512020708.C7Q0UXB2-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project b3428bb966f1de8aa48375ffee0eba04ede133b7)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251202/202512020708.C7Q0UXB2-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/202512020708.C7Q0UXB2-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0609]: no field `driver` on type `i2c_driver`
--> rust/kernel/i2c.rs:123:27
|
123 | (*idrv.get()).driver.name = name.as_char_ptr();
| ^^^^^^ unknown field
|
= note: available field is: `_address`
--
>> error[E0609]: no field `probe` on type `i2c_driver`
--> rust/kernel/i2c.rs:124:27
|
124 | (*idrv.get()).probe = Some(Self::probe_callback);
| ^^^^^ unknown field
|
= note: available field is: `_address`
--
>> error[E0609]: no field `remove` on type `i2c_driver`
--> rust/kernel/i2c.rs:125:27
|
125 | (*idrv.get()).remove = Some(Self::remove_callback);
| ^^^^^^ unknown field
|
= note: available field is: `_address`
--
>> error[E0609]: no field `shutdown` on type `i2c_driver`
--> rust/kernel/i2c.rs:126:27
|
126 | (*idrv.get()).shutdown = Some(Self::shutdown_callback);
| ^^^^^^^^ unknown field
|
= note: available field is: `_address`
--
>> error[E0609]: no field `id_table` on type `i2c_driver`
--> rust/kernel/i2c.rs:127:27
|
127 | (*idrv.get()).id_table = i2c_table;
| ^^^^^^^^ unknown field
|
= note: available field is: `_address`
--
>> error[E0609]: no field `driver` on type `i2c_driver`
--> rust/kernel/i2c.rs:128:27
|
128 | (*idrv.get()).driver.of_match_table = of_table;
| ^^^^^^ unknown field
|
= note: available field is: `_address`
--
>> error[E0609]: no field `driver` on type `i2c_driver`
--> rust/kernel/i2c.rs:129:27
|
129 | (*idrv.get()).driver.acpi_match_table = acpi_table;
| ^^^^^^ unknown field
|
= note: available field is: `_address`
--
>> error[E0609]: no field `dev` on type `i2c_client`
--> rust/kernel/i2c.rs:393:73
|
393 | unsafe { bindings::put_device(&raw mut (*obj.as_ref().as_raw()).dev) }
| ^^^ unknown field
|
= note: available field is: `_address`
--
>> error[E0609]: no field `dev` on type `i2c_client`
--> rust/kernel/i2c.rs:402:44
|
402 | let dev = unsafe { &raw mut (*raw).dev };
| ^^^ unknown field
|
= note: available field is: `_address`
--
>> error[E0609]: no field `dev` on type `i2c_client`
--> rust/kernel/i2c.rs:422:79
|
422 | let idev = unsafe { container_of!(dev.as_raw(), bindings::i2c_client, dev) };
| ^^^
|
= note: available field is: `_address`
--
>> error[E0609]: no field `dev` on type `i2c_client`
--> rust/kernel/i2c.rs:422:79
|
422 | let idev = unsafe { container_of!(dev.as_raw(), bindings::i2c_client, dev) };
| ^^^ unknown field
|
= note: available field is: `_address`
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-01 23:51 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=202512020708.C7Q0UXB2-lkp@intel.com \
--to=lkp@intel.com \
--cc=dakr@kernel.org \
--cc=igor.korotin.linux@gmail.com \
--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