From: kernel test robot <lkp@intel.com>
To: FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Miguel Ojeda <ojeda@kernel.org>,
Danilo Krummrich <dakr@kernel.org>
Subject: error[E0432]: unresolved import `core::sync::atomic::AtomicU64`
Date: Wed, 30 Apr 2025 12:54:10 +0800 [thread overview]
Message-ID: <202504301208.YQCguEmE-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 8bac8898fe398ffa3e09075ecea2be511725fb0b
commit: 584e61452f75bfeac2cdd83730b4059526ec60c7 rust: helpers: Remove volatile qualifier from io helpers
date: 2 weeks ago
config: um-randconfig-r063-20250430 (https://download.01.org/0day-ci/archive/20250430/202504301208.YQCguEmE-lkp@intel.com/config)
compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6)
rustc: rustc 1.78.0 (9b00956e5 2024-04-29)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250430/202504301208.YQCguEmE-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/202504301208.YQCguEmE-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error[E0432]: unresolved import `core::sync::atomic::AtomicU64`
--> rust/kernel/block/mq/operations.rs:15:33
|
15 | use core::{marker::PhantomData, sync::atomic::AtomicU64, sync::atomic::Ordering};
| ^^^^^^^^^^^^^^---------
| | |
| | help: a similar name exists in the module: `AtomicU32`
| no `AtomicU64` in `sync::atomic`
--
>> error[E0432]: unresolved import `core::sync::atomic::AtomicU64`
--> rust/kernel/block/mq/request.rs:16:20
|
16 | sync::atomic::{AtomicU64, Ordering},
| ^^^^^^^^^
| |
| no `AtomicU64` in `sync::atomic`
| help: a similar name exists in the module: `AtomicU32`
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-04-30 4:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 4:54 kernel test robot [this message]
2025-04-30 5:06 ` error[E0432]: unresolved import `core::sync::atomic::AtomicU64` Miguel Ojeda
2025-04-30 8:28 ` Andreas Hindborg
-- strict thread matches above, loose matches on Subject: below --
2025-06-08 0:21 kernel test robot
2025-06-27 7:06 kernel test robot
2025-11-20 20:32 kernel test robot
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=202504301208.YQCguEmE-lkp@intel.com \
--to=lkp@intel.com \
--cc=dakr@kernel.org \
--cc=fujita.tomonori@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@kernel.org \
/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