[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72nvzdypum2jZ535tWiWU_Dd30cBPSfODXKC8K+VA1uHNg@mail.gmail.com>
Date: Fri, 30 Jan 2026 21:42:28 +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, Daniel Almeida <daniel.almeida@...labora.com>,
Fiona Behrens <me@...enk.dev>
Subject: Re: [PATCH 0/4] scripts: generate_rust_analyzer.py: tidy and add type hints
On Fri, Jan 30, 2026 at 9:32 PM Tamir Duberstein <tamird@...nel.org> wrote:
>
> Apologies for the whiplash, I reset the branch back to rc7. In the
> meantime, these commits are available in
> https://github.com/tamird/linux/tree/ra-next for folks working on the
> next round of improvements.
No worries at all, there is no harm done (linux-next was already done
today, and it will likely be closed until Monday).
We can go through the usual timelines and how to prepare a PR etc. in
the call (i.e. the usual bits I explain to new maintainers -- in the
first call we didn't have time for much).
Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists