[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72nPdcU=E98pE=WM_e=0HPDY7Evg_pto87kf6N58uYbYtQ@mail.gmail.com>
Date: Wed, 13 Nov 2024 00:47:41 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Miguel Ojeda <ojeda@...nel.org>
Cc: Alex Gaynor <alex.gaynor@...il.com>, Nathan Chancellor <nathan@...nel.org>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>, rust-for-linux@...r.kernel.org,
Nick Desaulniers <ndesaulniers@...gle.com>, Bill Wendling <morbo@...gle.com>,
Justin Stitt <justinstitt@...gle.com>, llvm@...ts.linux.dev, linux-kernel@...r.kernel.org,
patches@...ts.linux.dev, Ben Beasley <code@...icinmybrain.net>,
NoisyCoil <noisycoil@...anota.com>, Matthias Geiger <werdahias@...eup.net>
Subject: Re: [PATCH v2] rust: warn on bindgen < 0.69.5 and libclang >= 19.1
On Mon, Nov 11, 2024 at 9:16 PM Miguel Ojeda <ojeda@...nel.org> wrote:
>
> We would like to put this into the merge window, or ideally very soon after as a
> "fix" (it is not really a fix, but it is very convenient for people wondering
> why their toolchain may not work, especially if tracepoints land in the merge
> window as expected).
Applied to `rust-next` (tentatively) -- thanks everyone!
I will wait a few days, and if no one objects, I will include it in the
PR. Otherwise, I will remove it (it is the last commit for
`rust-next`).
Cheers,
Miguel
Powered by blists - more mailing lists