From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Markus Probst <markus.probst@posteo.de>
Cc: "Lee Jones" <lee@kernel.org>, "Pavel Machek" <pavel@kernel.org>,
"Danilo Krummrich" <dakr@kernel.org>,
"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: Sun, 9 Nov 2025 11:25:03 +0100 [thread overview]
Message-ID: <CANiq72mmb7oH_3bj8_EwMA8RGg6M9TjWj+ebbaEQV-RxLx1iBw@mail.gmail.com> (raw)
In-Reply-To: <d0f1effa5352959191ea8525963e84a832026dee.camel@posteo.de>
On Sat, Nov 8, 2025 at 3:49 PM Markus Probst <markus.probst@posteo.de> wrote:
>
> Could you please clarify if there would be other responsibilities to it
> than code reviews and adapting the code to breaking changes from the
> LED Subsystem (I assume I will be notified in that event).
It depends on the case, e.g. if the LED maintainers prefer that you
manage your own tree and send PRs to them.
But, generally speaking, a kernel maintainer takes care of a few more
things, e.g. triaging bugs, fixing issues, tracking patches, deciding
which releases a patch should go into (backporting), etc. Some details
at:
https://docs.kernel.org/maintainer/feature-and-driver-maintainers.html#responsibilities
This is not meant to discourage you, of course -- being a kernel
maintainer is a fairly unique experience. Now, how much it is wildly
varies depending on what code it is, e.g. how many changes go through
the C side, how many users/callers you have etc.
I hope that helps!
Cheers,
Miguel
next prev parent reply other threads:[~2025-11-09 10:25 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 ` [PATCH v7 0/2] rust: leds: add " Danilo Krummrich
2025-10-30 18:07 ` Markus Probst
2025-10-31 13:18 ` Miguel Ojeda
2025-11-08 14:49 ` Markus Probst
2025-11-09 10:25 ` Miguel Ojeda [this message]
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=CANiq72mmb7oH_3bj8_EwMA8RGg6M9TjWj+ebbaEQV-RxLx1iBw@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--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=dakr@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).