From: kernel test robot <lkp@intel.com>
To: Beata Michalska <beata.michalska@arm.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>
Subject: [tiwai-sound:test/sound-rust-v7.3 7/56] error[E0425]: cannot find function `pm_runtime_barrier` in crate `bindings`
Date: Thu, 05 Nov 2026 22:25:47 +0100 [thread overview]
Message-ID: <202611052257.izHDrnRN-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git test/sound-rust-v7.3
head: 070444a8abf14da700680a5331d0a95cd11e578b
commit: d5dd8d4a1fbe95ad79dc47b8b6606b6fcece0c82 [7/56] rust: add runtime PM support
config: s390-randconfig-2000-20261105 (https://download.01.org/0day-ci/archive/20261105/202611052257.izHDrnRN-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 0fa861dbbf46e5a75f621406fd91cb015d8754bf)
rustc: rustc 1.96.0 (ac68faa20 2026-05-25)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261105/202611052257.izHDrnRN-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/202611052257.izHDrnRN-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
>> error[E0425]: cannot find function `pm_runtime_barrier` in crate `bindings`
--> rust/kernel/pm.rs:1004:23
|
1004 | bindings::pm_runtime_barrier(self.ctx.inner.dev.as_raw());
| ^^^^^^^^^^^^^^^^^^
|
::: rust/bindings/bindings_helpers_generated.rs:1555:5
|
1555 | pub fn pm_runtime_active(dev: *mut device) -> bool_;
| ---------------------------------------------------- similarly named function `pm_runtime_active` defined here
|
help: a function with a similar name exists
|
1004 - bindings::pm_runtime_barrier(self.ctx.inner.dev.as_raw());
1004 + bindings::pm_runtime_active(self.ctx.inner.dev.as_raw());
|
--
>> warning: unused variable: `dev`
--> rust/kernel/pm.rs:380:15
|
380 | fn active(dev: &device::Device<device::Bound>) -> bool {
| ^^^ help: if this is intentional, prefix it with an underscore: `_dev`
|
= note: `#[warn(unused_variables)]` (part of `#[warn(unused)]`) on by default
--
>> warning: unused variable: `dev`
--> rust/kernel/pm.rs:385:18
|
385 | fn suspended(dev: &device::Device<device::Bound>) -> bool {
| ^^^ help: if this is intentional, prefix it with an underscore: `_dev`
--
>> warning: unused variable: `dev`
--> rust/kernel/pm.rs:408:22
|
408 | fn get_if_active(dev: &device::Device<device::Bound>) -> Result {
| ^^^ help: if this is intentional, prefix it with an underscore: `_dev`
--
>> warning: unused variable: `dev`
--> rust/kernel/pm.rs:416:24
|
416 | fn runtime_disable(dev: &device::Device<device::Bound>) {}
| ^^^ help: if this is intentional, prefix it with an underscore: `_dev`
--
>> error[E0425]: cannot find function `__pm_runtime_disable` in crate `bindings`
--> rust/kernel/pm.rs:1003:23
|
1003 | bindings::__pm_runtime_disable(self.ctx.inner.dev.as_raw(), true);
| ^^^^^^^^^^^^^^^^^^^^ not found in `bindings`
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-11-05 21:25 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=202611052257.izHDrnRN-lkp@intel.com \
--to=lkp@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=beata.michalska@arm.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tiwai@suse.de \
/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