[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72kN_QjYSCdzs9UCx2sHdR9Q2g_7_h-ZZ2y0qLZjhUxX6g@mail.gmail.com>
Date: Mon, 24 Nov 2025 15:51:46 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Boqun Feng <boqun.feng@...il.com>, Stephen Rothwell <sfr@...b.auug.org.au>,
Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...nel.org>, "H. Peter Anvin" <hpa@...or.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>, ojeda@...nel.org,
Danilo Krummrich <dakr@...nel.org>, Alexandre Courbot <acourbot@...dia.com>, nouveau@...ts.freedesktop.org,
Alice Ryhl <aliceryhl@...gle.com>
Subject: Re: linux-next: build failure after merge of the tip tree
On Mon, Nov 24, 2025 at 3:47 PM Peter Zijlstra <peterz@...radead.org> wrote:
>
> I really don't think rustavailable is doing a good job here. Strictly
> speaking yes, its available, but figuring out why things don't work is a
> giant pain in the arse.
I guess `rusttoolchainavailable` would have been a better name, i.e.
it is only about the toolchain, not about the kernel config
requirements:
rustavailable - Checks whether the Rust toolchain is
available and, if not, explains why.
> Now, lets see if frobbing Kconfig to disqualify RANDSTRUCT will let
> allmodconfig work better.
By the way, I have had this patch around for RANDSTRUCT a long time:
https://lore.kernel.org/rust-for-linux/20241119185747.862544-1-ojeda@kernel.org/
More than glad if someone confirms it works for them...
Cheers,
Miguel
Powered by blists - more mailing lists