[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72=B=ZWJC8b3Zrb1hAJ7S86sH4UNDJPa=dR80tTgtQtZ5A@mail.gmail.com>
Date: Thu, 15 Jan 2026 22:53:34 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Tamir Duberstein <tamird@...nel.org>
Cc: Jesung Yang <y.j3ms.n@...il.com>, Miguel Ojeda <ojeda@...nel.org>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] scripts: generate_rust_analyzer: compile sysroot with
correct edition
On Thu, Jan 15, 2026 at 10:36 PM Tamir Duberstein <tamird@...nel.org> wrote:
>
> Ah, thanks. If the prerequisite isn't backported, who provides the
> resolved patch?
The maintainers, typically, or perhaps authors of the patch -- when a
patch doesn't apply cleanly, the stable team sends an email to the
relevant people with instructions on the top, which then can used to
provide them with a resolution (essentially replying with a new
patch).
> Ack, I guess that will have to happen at apply time for this one?
Yeah, I can do that:
Cc: stable@...r.kernel.org
> Thanks Miguel.
You're welcome!
Cheers,
Miguel
Powered by blists - more mailing lists