From: "Danilo Krummrich" <dakr@kernel.org>
To: "Maxime Ripard" <mripard@kernel.org>
Cc: <aliceryhl@google.com>, <airlied@gmail.com>, <simona@ffwll.ch>,
<maarten.lankhorst@linux.intel.com>, <tzimmermann@suse.de>,
<acourbot@nvidia.com>, <daniel.almeida@collabora.com>,
<nouveau@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>,
<rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Add drm-rust tree for Rust DRM drivers and infrastructure
Date: Tue, 02 Sep 2025 19:49:56 +0200 [thread overview]
Message-ID: <DCII677CICRL.2OCMSV7ESGTQ5@kernel.org> (raw)
In-Reply-To: <humoafx7njwhvdwarelew2bwyl34q3ls5vbrkj6psfukoroni5@z7ap6mc4lj3k>
On Tue Sep 2, 2025 at 7:40 PM CEST, Maxime Ripard wrote:
> On Mon, Sep 01, 2025 at 10:26:39PM +0200, Danilo Krummrich wrote:
>> Multiple DRM Rust drivers (e.g. nova-core, nova-drm, Tyr, rvkms) are in
>> development, with at least Nova and (soon) Tyr already upstream. Having a
>> shared tree will ease and accelerate development, since all drivers can
>> consume new infrastructure in the same release cycle.
>>
>> This includes infrastructure shared with other subsystem trees (e.g. Rust
>> or driver-core). By consolidating in drm-rust, we avoid adding extra
>> burden to drm-misc maintainers, e.g. dealing with cross-tree topic
>> branches.
>>
>> The drm-misc tree is not a good fit for this stage of development, since
>> its documented scope is small drivers with occasional large series.
>>
>> Rust drivers in development upstream, however, regularly involve large
>> patch series, new infrastructure, and shared topic branches, which may
>> not align well with drm-misc at this stage.
>>
>> The drm-rust tree may not be a permanent solution. Once the core Rust,
>> DRM, and KMS infrastructure have stabilized, drivers and infrastructure
>> changes are expected to transition into drm-misc or standalone driver
>> trees respectively. Until then, drm-rust provides a dedicated place to
>> coordinate development without disrupting existing workflows too much.
>>
>> Cc: Alice Ryhl <aliceryhl@google.com>
>> Cc: David Airlie <airlied@gmail.com>
>> Cc: Simona Vetter <simona@ffwll.ch>
>> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>> Cc: Maxime Ripard <mripard@kernel.org>
>> Cc: Thomas Zimmermann <tzimmermann@suse.de>
>> Cc: Alexandre Courbot <acourbot@nvidia.com>
>> Cc: Daniel Almeida <daniel.almeida@collabora.com>
>> Signed-off-by: Danilo Krummrich <dakr@kernel.org>
>> ---
>> MAINTAINERS | 11 ++++++++++-
>> 1 file changed, 10 insertions(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index fe168477caa4..1cd6597c7f1d 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -8079,7 +8079,6 @@ F: Documentation/devicetree/bindings/gpu/
>> F: Documentation/gpu/
>> F: drivers/gpu/drm/
>> F: drivers/gpu/vga/
>> -F: rust/kernel/drm/
>> F: include/drm/drm
>> F: include/linux/vga*
>> F: include/uapi/drm/
>> @@ -8096,6 +8095,16 @@ X: drivers/gpu/drm/radeon/
>> X: drivers/gpu/drm/tegra/
>> X: drivers/gpu/drm/xe/
>>
>> +DRM DRIVERS AND COMMON INFRASTRUCTURE [RUST]
>> +M: Danilo Krummrich <dakr@kernel.org>
>> +M: Alice Ryhl <aliceryhl@google.com>
>> +S: Supported
>> +W: https://drm.pages.freedesktop.org/maintainer-tools/drm-rust.html
>> +T: git https://gitlab.freedesktop.org/drm/rust/kernel.git
>> +F: drivers/gpu/drm/nova/
>> +F: drivers/gpu/nova-core/
>> +F: rust/kernel/drm/
>> +
>
> Would it make sense to add the drm-misc maintainers as reviewers for the
> bindings?
This will get you all the driver patches in your inbox as well, maybe
discarding the following hunk is what we want instead?
@@ -8079,7 +8079,6 @@ F: Documentation/devicetree/bindings/gpu/
F: Documentation/gpu/
F: drivers/gpu/drm/
F: drivers/gpu/vga/
-F: rust/kernel/drm/
F: include/drm/drm
F: include/linux/vga*
F: include/uapi/drm/
> Either way,
>
> Acked-by: Maxime Ripard <mripard@kernel.org>
>
> Maxime
next prev parent reply other threads:[~2025-09-02 17:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 20:26 [PATCH] MAINTAINERS: Add drm-rust tree for Rust DRM drivers and infrastructure Danilo Krummrich
2025-09-02 8:39 ` Alice Ryhl
2025-09-02 11:08 ` Daniel Almeida
2025-09-02 11:25 ` Jani Nikula
2025-09-02 12:17 ` Alexandre Courbot
2025-09-02 17:40 ` Maxime Ripard
2025-09-02 17:49 ` Danilo Krummrich [this message]
2025-09-02 17:57 ` Maxime Ripard
2025-09-02 18:09 ` Danilo Krummrich
2025-09-03 15:21 ` Janne Grunau
2025-09-04 10:40 ` Alice Ryhl
2025-09-04 11:09 ` Danilo Krummrich
2025-09-04 15:26 ` Danilo Krummrich
2025-09-05 7:19 ` Alice Ryhl
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=DCII677CICRL.2OCMSV7ESGTQ5@kernel.org \
--to=dakr@kernel.org \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=daniel.almeida@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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).