From: "Danilo Krummrich" <dakr@kernel.org>
To: "Markus Probst" <markus.probst@posteo.de>,
"Lee Jones" <lee@kernel.org>, "Pavel Machek" <pavel@kernel.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Dave Ertman" <david.m.ertman@intel.com>,
"Ira Weiny" <ira.weiny@intel.com>,
"Leon Romanovsky" <leon@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
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>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
rust-for-linux@vger.kernel.org, linux-leds@vger.kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/2] rust: leds: add led classdev abstractions
Date: Thu, 30 Oct 2025 11:52:40 +0100 [thread overview]
Message-ID: <DDVLMBC40199.2BVFYHDGQP4Q4@kernel.org> (raw)
In-Reply-To: <20251027200547.1038967-1-markus.probst@posteo.de>
Hi Markus,
On Mon Oct 27, 2025 at 9:06 PM CET, Markus Probst wrote:
> Markus Probst (2):
> rust: Add trait to convert a device reference to a bus device
> reference
> rust: leds: add basic led classdev abstractions
I don't see an entry in the MAINTAINERS file for the added LED code.
Did you hear back from the LED maintainers already?
@Lee, Pavel: What's your take on this?
Depending on whether it is likely for the LED work to land in this cycle, I'd
otherwise pick the first patch into the driver-core tree for now, since it can
already be used in the PCI and platform code.
(I'd assume you want to wait for the driver from [1] before picking the Rust LED
code, which has to wait for the next cycle since it depends on the Rust I2C
code.)
[1] https://lore.kernel.org/rust-for-linux/20251008181027.662616-1-markus.probst@posteo.de/
next prev parent reply other threads:[~2025-10-30 10:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 20:06 [PATCH v7 0/2] rust: leds: add led classdev abstractions Markus Probst
2025-10-27 20:06 ` [PATCH v7 1/2] rust: Add trait to convert a device reference to a bus device reference Markus Probst
2025-11-17 22:04 ` Danilo Krummrich
2025-10-27 20:06 ` [PATCH v7 2/2] rust: leds: add basic led classdev abstractions Markus Probst
2025-10-30 10:52 ` Danilo Krummrich [this message]
2025-10-30 18:07 ` [PATCH v7 0/2] rust: leds: add " Markus Probst
2025-10-31 13:18 ` Miguel Ojeda
2025-11-08 14:49 ` Markus Probst
2025-11-09 10:25 ` Miguel Ojeda
2025-11-10 13:40 ` Lee Jones
2025-11-13 14:17 ` Markus Probst
2025-11-13 14:20 ` Markus Probst
2025-11-13 14:43 ` Markus Probst
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=DDVLMBC40199.2BVFYHDGQP4Q4@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=david.m.ertman@intel.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=ira.weiny@intel.com \
--cc=kwilczynski@kernel.org \
--cc=lee@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=tmgross@umich.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.