Re: [tip:locking/core 1/13] error[E0425]: cannot find function `atomic_add` in crate `bindings`

[Boqun Feng <boqun.feng@gmail.com>]

Hi Peter,

On Sat, Sep 13, 2025 at 04:00:27PM +0200, 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

I think we are missing this patch:

	https://lore.kernel.org/rust-for-linux/20250905044141.77868-2-boqun.feng@gmail.com/

in locking/core. It should be applied before all atomic patches.

Regards,
Boqun

> config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250913/202509131610.IPwv7fy3-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/20250913/202509131610.IPwv7fy3-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/202509131610.IPwv7fy3-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)
> --
[...]