[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <228245d0-4620-48c7-b4bd-532bb873bdf2@leemhuis.info>
Date: Wed, 17 Sep 2025 09:58:54 +0200
From: Thorsten Leemhuis <linux@...mhuis.info>
To: Dan Carpenter <dan.carpenter@...aro.org>,
Christian Heusel <christian@...sel.eu>, Mark Brown <broonie@...nel.org>
Cc: Naresh Kamboju <naresh.kamboju@...aro.org>,
rust-for-linux@...r.kernel.org, open list <linux-kernel@...r.kernel.org>,
Linux Regressions <regressions@...ts.linux.dev>,
lkft-triage@...ts.linaro.org, Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>, Boqun Feng <boqun.feng@...il.com>,
Peter Zijlstra <peterz@...radead.org>, Alice Ryhl <aliceryhl@...gle.com>,
Benno Lossin <lossin@...nel.org>, Elle Rhumsaa <elle@...thered-steel.dev>,
Arnd Bergmann <arnd@...db.de>, Anders Roxell <anders.roxell@...aro.org>,
Ben Copeland <benjamin.copeland@...aro.org>
Subject: Re: next-20250915: error[E0425]: cannot find function
`atomic_read_acquire` in crate `bindings`
On 17.09.25 09:42, Dan Carpenter wrote:
> On Tue, Sep 16, 2025 at 06:46:06PM +0200, Christian Heusel wrote:
>> On 25/09/16 09:56PM, Naresh Kamboju wrote:
>>> On Tue, 16 Sept 2025 at 11:17, Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
>>>>
>>>> The following build warnings / errors noticed on the arm arm64 and x86_64
>>>> with rust config build on the Linux next-20250915 tag.
>>>>
>>>> First seen on next-20250915
>>>> Good: next-20250912
>>>> Bad: next-20250915
> [...]
>>>> Build regression: next-20250915: error[E0425]: cannot find function
>>>> `atomic_read_acquire` in crate `bindings`
>>>
>>> Anders bisected this build regressions and found,
>>>
>>> # first bad commit:
>>> [eb57133305f61b612252382d0c1478bba7f57b67]
>>> rust: sync: Add basic atomic operation mapping framework
>>
>> Is this still an issue on next-20250916?
FWIW, I ran into this on next-20250915 and it afaics was fixed for
next-20250916.
>> As far as I can tell this has
>> been fixed, but now there is another rust build issue, see
>> https://lore.kernel.org/regressions/0fee48bb-7411-4414-b4e7-395a8c3d0f6c@heusel.eu/
>> for more information.
>
> next-20250916 still fails but with a different Rust issue.
Ran into that that merge mistake, too, but that can be fixed by the
patch Christian linked to above -- and I expect Mark (now CCed) has
seen it and will resolve this with today's -next.
> [...]
Ciao, Thorsten
Powered by blists - more mailing lists