From: Peter Zijlstra <peterz@infradead.org>
To: Boqun Feng <boqun.feng@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
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:41:33 +0200 [thread overview]
Message-ID: <20250915074133.GF1386988@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250915073345.GR3419281@noisy.programming.kicks-ass.net>
On Mon, Sep 15, 2025 at 09:33:45AM +0200, Peter Zijlstra wrote:
> On Sat, Sep 13, 2025 at 08:23:01AM -0700, Boqun Feng wrote:
> > 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.
>
> Ah, let me go fix things.
I've no idea how that first patch went walk-about. But hopefully I got
it right now..
next prev parent reply other threads:[~2025-09-15 7:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-13 14:00 [tip:locking/core 1/13] error[E0425]: cannot find function `atomic_add` in crate `bindings` kernel test robot
2025-09-13 15:23 ` Boqun Feng
2025-09-15 7:33 ` Peter Zijlstra
2025-09-15 7:41 ` Peter Zijlstra [this message]
2025-09-16 0:13 ` Boqun Feng
-- strict thread matches above, loose matches on Subject: below --
2025-09-14 6:10 kernel test robot
2025-09-15 7:32 ` Peter Zijlstra
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=20250915074133.GF1386988@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.