From: kernel test robot <lkp@intel.com>
To: Lyude Paul <lyude@redhat.com>, rust-for-linux@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
"Danilo Krummrich" <dakr@redhat.com>,
airlied@redhat.com, "Ingo Molnar" <mingo@redhat.com>,
"Will Deacon" <will@kernel.org>,
"Waiman Long" <longman@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@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@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Martin Rodriguez Reboredo" <yakoyoku@gmail.com>,
"Valentin Obst" <kernel@valentinobst.de>
Subject: Re: [PATCH v2 1/1] rust: sync: Add Lock::from_raw() for Lock<(), B>
Date: Sat, 21 Sep 2024 22:52:41 +0800 [thread overview]
Message-ID: <202409212236.CKCTlTCJ-lkp@intel.com> (raw)
In-Reply-To: <20240916231817.643934-4-lyude@redhat.com>
Hi Lyude,
kernel test robot noticed the following build warnings:
[auto build test WARNING on a2f11547052001bd448ccec81dd1e68409078fbb]
url: https://github.com/intel-lab-lkp/linux/commits/Lyude-Paul/rust-sync-Add-Lock-from_raw-for-Lock-B/20240917-071956
base: a2f11547052001bd448ccec81dd1e68409078fbb
patch link: https://lore.kernel.org/r/20240916231817.643934-4-lyude%40redhat.com
patch subject: [PATCH v2 1/1] rust: sync: Add Lock::from_raw() for Lock<(), B>
config: x86_64-randconfig-104-20240921 (https://download.01.org/0day-ci/archive/20240921/202409212236.CKCTlTCJ-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240921/202409212236.CKCTlTCJ-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/202409212236.CKCTlTCJ-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> warning: unused import: `mem`
--> rust/kernel/sync/lock.rs:10:74
|
10 | use core::{cell::UnsafeCell, marker::PhantomData, marker::PhantomPinned, mem};
| ^^^
|
= note: `#[warn(unused_imports)]` on by default
--
>> warning: unused import: `prelude`
--> rust/kernel/sync/lock.rs:9:38
|
9 | use crate::{init::PinInit, pin_init, prelude::*, str::CStr, types::Opaque, types::ScopeGuard};
| ^^^^^^^
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-09-21 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 23:17 [PATCH v2 0/1] rust: sync: Add Lock::from_raw for Lock<(), B> Lyude Paul
2024-09-16 23:17 ` [PATCH v2 1/1] rust: sync: Add Lock::from_raw() " Lyude Paul
2024-09-21 14:52 ` kernel test robot [this message]
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=202409212236.CKCTlTCJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=a.hindborg@samsung.com \
--cc=airlied@redhat.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@redhat.com \
--cc=gary@garyguo.net \
--cc=kernel@valentinobst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=lyude@redhat.com \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tmgross@umich.edu \
--cc=wedsonaf@gmail.com \
--cc=will@kernel.org \
--cc=yakoyoku@gmail.com \
/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