From: Rahul Rameshbabu <sergeantsagara@protonmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
"Benjamin Tissoires" <bentiss@kernel.org>,
"Jiri Kosina" <jikos@kernel.org>,
linux-input@vger.kernel.org, rust-for-linux@vger.kernel.org,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Daniel Brooks" <db48x@db48x.net>
Subject: Re: [PATCH v1 2/3] rust: core abstractions for HID drivers
Date: Sun, 06 Jul 2025 03:03:29 +0000 [thread overview]
Message-ID: <87y0t281hi.fsf@protonmail.com> (raw)
In-Reply-To: <CANiq72=+UUFVemSGHvzkX5FoOv-U5YRDKQkbKjYwqEfex-ey6w@mail.gmail.com>
On Sat, 05 Jul, 2025 12:41:02 +0200 "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com> wrote:
> On Sat, Jul 5, 2025 at 9:31 AM Rahul Rameshbabu
> <sergeantsagara@protonmail.com> wrote:
>>
>> From what I can tell,
>
> I think Benjamin wants to keep an eye on things but may not have much
> time to take care of patches and so on.
>
> So it sounds like having a separate `MAINTAINERS` subentry under them
> is best, with you applying patches and then sending PRs to them.
>
> That way, they remain in control, they can coordinate any changes that
> involve both the C and the Rust side if any, and so on; while they
> don't need to handle directly Rust patches themselves, fixing issues
> with the Rust side, etc., thus removing work from their side; i.e. you
> would be doing that since you want to drive and use those Rust
> abstractions.
>
> That arrangement is great and what other subsystems have done (most of
> the entries with "... [RUST]"). It also helps more people
> involved/trained in the overall subsystem too (should they want more
> reviewers/maintainers), and also allows you to become a maintainer
> yourself, learning to send PRs, etc. (which you may welcome -- if you
> already took patches, sent PRs etc., then please excuse me! I only did
> a quick search so I may have missed it.)
Thanks Miguel. I would really enjoy the opportunity. Like you noticed, I
do not have this experience on the mailing list. I also want to give
Benjamin and Jiri time to consider these options. Let me get my v2
patches sent out in the meantime.
Thanks,
Rahul Rameshbabu
>
> We try to reserve the global Rust tree fallback for cases where there
> is really no other way, e.g. when a key subsystem doesn't want
> anything to do with Rust at all and thus would block many others
> otherwise.
>
> Thanks!
>
> Cheers,
> Miguel
next prev parent reply other threads:[~2025-07-06 3:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 4:51 [PATCH v1 0/3] Initial work for Rust abstraction for HID device driver development Rahul Rameshbabu
2025-06-29 4:51 ` [PATCH v1 1/3] HID: core: Change hid_driver to use a const char* for name Rahul Rameshbabu
2025-06-29 4:51 ` [PATCH v1 2/3] rust: core abstractions for HID drivers Rahul Rameshbabu
2025-06-29 8:45 ` Danilo Krummrich
2025-07-03 6:37 ` Jiri Kosina
2025-07-03 8:01 ` Benjamin Tissoires
2025-07-03 8:20 ` Danilo Krummrich
2025-07-05 7:31 ` Rahul Rameshbabu
2025-07-05 10:41 ` Miguel Ojeda
2025-07-06 3:03 ` Rahul Rameshbabu [this message]
2025-07-05 10:54 ` Danilo Krummrich
2025-06-29 4:51 ` [PATCH v1 3/3] rust: hid: Glorious Gaming PC Race Model O and O- mice reference driver Rahul Rameshbabu
2025-06-29 9:22 ` Danilo Krummrich
2025-07-03 10:36 ` Peter Hutterer
2025-07-05 13:01 ` [PATCH v1 0/3] Initial work for Rust abstraction for HID device driver development Aditya Garg
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=87y0t281hi.fsf@protonmail.com \
--to=sergeantsagara@protonmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bentiss@kernel.org \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=db48x@db48x.net \
--cc=gary@garyguo.net \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@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 NNTP newsgroup(s).