From: Andreas Hindborg <a.hindborg@kernel.org>
To: Miguel Ojeda <ojeda@kernel.org>,
Tamir Duberstein <tamird@gmail.com>,
Jesung Yang <y.j3ms.n@gmail.com>, Miguel Ojeda <ojeda@kernel.org>
Cc: "Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add "RUST [RUST-ANALYZER]" entry
Date: Fri, 16 Jan 2026 10:06:11 +0100 [thread overview]
Message-ID: <875x92exks.fsf@kernel.org> (raw)
In-Reply-To: <20260115214545.63262-1-ojeda@kernel.org>
"Miguel Ojeda" <ojeda@kernel.org> writes:
> This entry will handle the support for `rust-analyzer`, which at the
> moment is essentially about the `scripts/generate_rust_analyzer.py`
> script.
>
> It is one more subentry of the Rust subsystem. The new branch is
> already part of linux-next and will be used to send PRs to be merged
> into rust-next.
>
> Tamir and Jesung will take care of it. They have both been active around
> the `rust-analyzer` support for a while.
>
> Cc: Tamir Duberstein <tamird@gmail.com>
> Cc: Jesung Yang <y.j3ms.n@gmail.com>
> Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
Acked-by: Andreas Hindborg <a.hindborg@kernel.org>
Best regards,
Andreas Hindborg
next prev parent reply other threads:[~2026-01-16 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <QDFL6zfZfF0kRFHJTKFk18yqRzNTKHh4NRBvd8pHl97TalqvmobTbj94H8b2T5pAg-AugBbi-wlArVhiKRCjSg==@protonmail.internalid>
2026-01-15 21:45 ` [PATCH] MAINTAINERS: add "RUST [RUST-ANALYZER]" entry Miguel Ojeda
2026-01-15 21:48 ` Miguel Ojeda
2026-01-15 21:49 ` Tamir Duberstein
2026-01-26 2:04 ` Miguel Ojeda
2026-01-16 4:00 ` Jesung Yang
2026-01-16 9:06 ` Andreas Hindborg [this message]
2026-01-26 5:03 ` Miguel Ojeda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875x92exks.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@gmail.com \
--cc=tmgross@umich.edu \
--cc=y.j3ms.n@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox