From: Lee Jones <lee@kernel.org>
To: Markus Probst <markus.probst@posteo.de>
Cc: "Pavel Machek" <pavel@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Dave Ertman" <david.m.ertman@intel.com>,
"Leon Romanovsky" <leon@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Boqun Feng" <boqun@kernel.org>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Tamir Duberstein" <tamird@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Onur Özkan" <work@onurozkan.dev>,
"Ira Weiny" <iweiny@kernel.org>,
rust-for-linux@vger.kernel.org, linux-leds@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: To Lee, Pavel: Re: [PATCH v25 0/4] rust: leds: add led classdev abstractions
Date: Wed, 23 Sep 2026 08:50:15 +0100 [thread overview]
Message-ID: <20260923075015.GE3438784@google.com> (raw)
In-Reply-To: <0b51e27e1b2e16ac5bf5776c7c1704ca90857ec5.camel@posteo.de>
On Tue, 22 Sep 2026, Markus Probst wrote:
> @Lee, @Pavel:
>
> Hi,
>
> This message has already been posted once [1] and no reply has been
> sent. So I added your names to the subject line, so this message will
> hopefully make a difference.
>
> --- The contents of the original message:
>
> Regarding the leds rust abstraction patch series.
>
> Lee already mentioned he will take Rust patches into his tree if
> "quality Rust-specific Reviewed-by" trailers are present [2].
> Will this also apply for any subsequent patches (e.g. bug fixes)?
I'd be happy to either take them in or let you set-up your own
maintainer tree.
> Secondly, there hasn't been a comment on me taking the maintainer role
> for the Rust abstraction yet. If thats fine with you, I kindly ask you
> to ACK the patch adding the MAINTAINERS file entry [3].
Fine by me.
> I was told there have been cases in the past of maintainers leaving the
> kernel directly after code has been merged. To take away any fears that
> might exist, I can assure you I will take care of the Rust code.
>
> If there is a patch with breaking API changes on the C side, simply add
> me to Cc and I will fix the Rust side.
>
> The missing ACK on the patch adding the MAINTAINERS file entry [3] and
> the missing Reviewed-By Rust trailers should be the only blockers of
> this patch series.
Those are quite large blockers, but yes.
> Thanks
> - Markus Probst
>
> [1]
> https://lore.kernel.org/rust-for-linux/6c57e08a5f4aa9096711d14d82ece19fb68c893f.camel@posteo.de/
>
> [2]
> https://lore.kernel.org/linux-leds/20251110134058.GC1949330@google.com/
>
> [3]
> https://lore.kernel.org/linux-leds/20260903-rust_leds-v24-4-8d9e4c04db69@posteo.de/
--
Lee Jones
prev parent reply other threads:[~2026-09-23 7:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 16:15 Markus Probst
2026-09-13 16:15 ` [PATCH v25 1/4] rust: leds: add basic " Markus Probst
2026-09-13 16:15 ` [PATCH v25 2/4] rust: leds: add Mode trait Markus Probst
2026-09-13 16:24 ` Markus Probst
2026-09-13 16:15 ` [PATCH v25 3/4] rust: leds: add multicolor classdev abstractions Markus Probst
2026-09-13 16:15 ` [PATCH v25 4/4] MAINTAINERS: rust: leds: Add rust abstraction entry Markus Probst
2026-09-22 16:29 ` To Lee, Pavel: Re: [PATCH v25 0/4] rust: leds: add led classdev abstractions Markus Probst
2026-09-23 7:50 ` Lee Jones [this message]
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=20260923075015.GE3438784@google.com \
--to=lee@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=david.m.ertman@intel.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=iweiny@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=markus.probst@posteo.de \
--cc=ojeda@kernel.org \
--cc=pavel@kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
/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
all inboxes | Powered by JetHome®