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>,
"Benno Lossin" <benno.lossin@proton.me>,
"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>
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 v6 1/2] rust: regulator: add a bare minimum regulator abstraction
Date: Sun, 29 Jun 2025 21:10:47 +0800 [thread overview]
Message-ID: <202506292009.nbvCCbAr-lkp@intel.com> (raw)
In-Reply-To: <20250627-topics-tyr-regulator-v6-1-1d015219b454@collabora.com>
Hi Daniel,
kernel test robot noticed the following build warnings:
[auto build test WARNING on edc5e6e019c99b529b3d1f2801d5cce9924ae79b]
url: https://github.com/intel-lab-lkp/linux/commits/Daniel-Almeida/rust-regulator-add-a-bare-minimum-regulator-abstraction/20250628-011418
base: edc5e6e019c99b529b3d1f2801d5cce9924ae79b
patch link: https://lore.kernel.org/r/20250627-topics-tyr-regulator-v6-1-1d015219b454%40collabora.com
patch subject: [PATCH v6 1/2] rust: regulator: add a bare minimum regulator abstraction
config: x86_64-randconfig-008-20250629 (https://download.01.org/0day-ci/archive/20250629/202506292009.nbvCCbAr-lkp@intel.com/config)
compiler: clang version 20.1.7 (https://github.com/llvm/llvm-project 6146a88f60492b520a36f8f8f3231e15f3cc6082)
rustc: rustc 1.78.0 (9b00956e5 2024-04-29)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250629/202506292009.nbvCCbAr-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/202506292009.nbvCCbAr-lkp@intel.com/
All warnings (new ones prefixed by >>):
***
*** Rust bindings generator 'bindgen' < 0.69.5 together with libclang >= 19.1
*** may not work due to a bug (https://github.com/rust-lang/rust-bindgen/pull/2824),
*** unless patched (like Debian's).
*** Your bindgen version: 0.65.1
*** Your libclang version: 20.1.7
***
***
*** Please see Documentation/rust/quick-start.rst for details
*** on how to set up the Rust support.
***
>> warning: variable does not need to be mutable
--> rust/kernel/regulator.rs:295:29
|
295 | pub fn try_into_enabled(mut self) -> Result<Regulator<Enabled>, Error<Disabled>> {
| ----^^^^
| |
| help: remove this `mut`
|
= note: `#[warn(unused_mut)]` on by default
--
>> warning: variable does not need to be mutable
--> rust/kernel/regulator.rs:324:30
|
324 | pub fn try_into_disabled(mut self) -> Result<Regulator<Disabled>, Error<Enabled>> {
| ----^^^^
| |
| help: remove this `mut`
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-06-29 13:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 17:11 [PATCH v6 0/2] Add a bare-minimum Regulator abstraction Daniel Almeida
2025-06-27 17:11 ` [PATCH v6 1/2] rust: regulator: add a bare minimum regulator abstraction Daniel Almeida
2025-06-29 13:10 ` kernel test robot [this message]
2025-07-02 10:35 ` Alice Ryhl
2025-07-02 13:03 ` Daniel Almeida
2025-07-02 13:12 ` Alice Ryhl
2025-07-02 13:14 ` Daniel Almeida
2025-06-27 17:11 ` [PATCH v6 2/2] MAINAINTERS: add regulator.rs to the regulator API entry Daniel Almeida
2025-07-01 15:28 ` [PATCH v6 0/2] Add a bare-minimum Regulator abstraction Daniel Almeida
2025-07-01 15:34 ` Mark Brown
2025-07-01 16:09 ` Daniel Almeida
2025-07-01 18:22 ` Miguel Ojeda
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=202506292009.nbvCCbAr-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=benno.lossin@proton.me \
--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=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®