From: kernel test robot <lkp@intel.com>
To: "Daniel Almeida" <daniel.almeida@collabora.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Boris Brezillon" <bbrezillon@kernel.org>,
"Sebastian Reichel" <sebastian.reichel@collabora.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Benno Lossin" <lossin@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
Daniel Almeida <daniel.almeida@collabora.com>
Subject: Re: [PATCH v7 1/2] rust: regulator: add a bare minimum regulator abstraction
Date: Sun, 6 Jul 2025 08:39:07 +0800 [thread overview]
Message-ID: <202507060837.ziqhqXVk-lkp@intel.com> (raw)
In-Reply-To: <20250704-topics-tyr-regulator-v7-1-77bfca2e22dc@collabora.com>
Hi Daniel,
kernel test robot noticed the following build errors:
[auto build test ERROR on 2009a2d5696944d85c34d75e691a6f3884e787c0]
url: https://github.com/intel-lab-lkp/linux/commits/Daniel-Almeida/rust-regulator-add-a-bare-minimum-regulator-abstraction/20250705-024526
base: 2009a2d5696944d85c34d75e691a6f3884e787c0
patch link: https://lore.kernel.org/r/20250704-topics-tyr-regulator-v7-1-77bfca2e22dc%40collabora.com
patch subject: [PATCH v7 1/2] rust: regulator: add a bare minimum regulator abstraction
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250706/202507060837.ziqhqXVk-lkp@intel.com/config)
compiler: clang version 20.1.7 (https://github.com/llvm/llvm-project 6146a88f60492b520a36f8f8f3231e15f3cc6082)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250706/202507060837.ziqhqXVk-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/202507060837.ziqhqXVk-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0425]: cannot find function `regulator_set_voltage` in crate `bindings`
--> rust/kernel/regulator.rs:258:23
|
258 | bindings::regulator_set_voltage(self.inner.as_ptr(), min_uv.0, max_uv.0)
| ^^^^^^^^^^^^^^^^^^^^^ not found in `bindings`
--
>> error[E0425]: cannot find function `regulator_get_voltage` in crate `bindings`
--> rust/kernel/regulator.rs:265:42
|
265 | let voltage = unsafe { bindings::regulator_get_voltage(self.inner.as_ptr()) };
| ^^^^^^^^^^^^^^^^^^^^^ not found in `bindings`
--
>> error[E0425]: cannot find function `regulator_get` in crate `bindings`
--> rust/kernel/regulator.rs:276:53
|
276 | let inner = from_err_ptr(unsafe { bindings::regulator_get(dev.as_raw(), name.as_ptr()) })?;
| ^^^^^^^^^^^^^ not found in `bindings`
--
>> error[E0425]: cannot find function `regulator_enable` in crate `bindings`
--> rust/kernel/regulator.rs:290:38
|
290 | to_result(unsafe { bindings::regulator_enable(self.inner.as_ptr()) })
| ^^^^^^^^^^^^^^^^ not found in `bindings`
--
>> error[E0425]: cannot find function `regulator_disable` in crate `bindings`
--> rust/kernel/regulator.rs:295:38
|
295 | to_result(unsafe { bindings::regulator_disable(self.inner.as_ptr()) })
| ^^^^^^^^^^^^^^^^^ not found in `bindings`
--
>> error[E0425]: cannot find function `regulator_is_enabled` in crate `bindings`
--> rust/kernel/regulator.rs:379:28
|
379 | unsafe { bindings::regulator_is_enabled(self.inner.as_ptr()) != 0 }
| ^^^^^^^^^^^^^^^^^^^^ not found in `bindings`
--
>> error[E0425]: cannot find function `regulator_disable` in crate `bindings`
--> rust/kernel/regulator.rs:389:32
|
389 | unsafe { bindings::regulator_disable(self.inner.as_ptr()) };
| ^^^^^^^^^^^^^^^^^ not found in `bindings`
--
>> error[E0425]: cannot find function `regulator_put` in crate `bindings`
--> rust/kernel/regulator.rs:393:28
|
393 | unsafe { bindings::regulator_put(self.inner.as_ptr()) };
| ^^^^^^^^^^^^^ not found in `bindings`
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-07-06 0:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 18:43 [PATCH v7 0/2] Add a bare-minimum Regulator abstraction Daniel Almeida
2025-07-04 18:43 ` [PATCH v7 1/2] rust: regulator: add a bare minimum regulator abstraction Daniel Almeida
2025-07-06 0:39 ` kernel test robot [this message]
2025-07-07 16:23 ` Daniel Almeida
2025-07-07 5:39 ` Alexandre Courbot
2025-07-04 18:43 ` [PATCH v7 2/2] MAINAINTERS: add regulator.rs to the regulator API entry Daniel Almeida
2025-07-07 5:39 ` Alexandre Courbot
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=202507060837.ziqhqXVk-lkp@intel.com \
--to=lkp@intel.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bbrezillon@kernel.org \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lossin@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=tmgross@umich.edu \
/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
all inboxes | Powered by JetHome®