From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: Boqun Feng <boqun.feng@gmail.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, x86@kernel.org,
Alice Ryhl <aliceryhl@google.com>,
Benno Lossin <lossin@kernel.org>,
Elle Rhumsaa <elle@weathered-steel.dev>
Subject: Re: [tip:locking/core 1/13] error[E0425]: cannot find function `atomic_add` in crate `bindings`
Date: Mon, 15 Sep 2025 09:32:45 +0200 [thread overview]
Message-ID: <20250915073245.GQ3419281@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <202509141437.5iiM1sOF-lkp@intel.com>
On Sun, Sep 14, 2025 at 02:10:26PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/core
> head: 502ae97746ab6d7b7b48d54b6a85a11815f390d0
> commit: eb57133305f61b612252382d0c1478bba7f57b67 [1/13] rust: sync: Add basic atomic operation mapping framework
> config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250914/202509141437.5iiM1sOF-lkp@intel.com/config)
> compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
> rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250914/202509141437.5iiM1sOF-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/202509141437.5iiM1sOF-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> error[E0425]: cannot find function `atomic_read_acquire` in crate `bindings`
> --> rust/kernel/sync/atomic/internal.rs:124:37
> |
> 124 | $unsafe { bindings::[< $ctype _ $func >]($($c_arg,)*) }
> | ^^^^^^^^^^^^^^^^^^^^ not found in `bindings`
> ...
> 201 | / declare_and_impl_atomic_methods!(
> 202 | | /// Basic atomic operations
> 203 | | pub trait AtomicBasicOps {
> 204 | | /// Atomic read (load).
> ... |
> 216 | | );
> | |_- in this macro invocation
> |
> = note: this error originates in the macro `impl_atomic_method` which comes from the expansion of the macro `declare_and_impl_atomic_methods` (in Nightly builds, run with -Z macro-backtrace for more info)
Boqun, did I mess things up? I can rebase this tree, but I've no real
clue with this rust stuff.
next prev parent reply other threads:[~2025-09-15 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-14 6:10 [tip:locking/core 1/13] error[E0425]: cannot find function `atomic_add` in crate `bindings` kernel test robot
2025-09-15 7:32 ` Peter Zijlstra [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-13 14:00 kernel test robot
2025-09-13 15:23 ` Boqun Feng
2025-09-15 7:33 ` Peter Zijlstra
2025-09-15 7:41 ` Peter Zijlstra
2025-09-16 0:13 ` Boqun Feng
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=20250915073245.GQ3419281@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=aliceryhl@google.com \
--cc=boqun.feng@gmail.com \
--cc=elle@weathered-steel.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=lossin@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=x86@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