lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <enuksb2qk5wyrilz3l2vnog45lghgmplrav5to6pd5k5owi36h@pxdq6y5dpgpt>
Date: Tue, 2 Sep 2025 19:57:38 +0200
From: Maxime Ripard <mripard@...nel.org>
To: Danilo Krummrich <dakr@...nel.org>
Cc: aliceryhl@...gle.com, airlied@...il.com, simona@...ll.ch, 
	maarten.lankhorst@...ux.intel.com, tzimmermann@...e.de, acourbot@...dia.com, 
	daniel.almeida@...labora.com, nouveau@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org, 
	rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add drm-rust tree for Rust DRM drivers and
 infrastructure

On Tue, Sep 02, 2025 at 07:49:56PM +0200, Danilo Krummrich wrote:
> 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@...gle.com>
> >> Cc: David Airlie <airlied@...il.com>
> >> Cc: Simona Vetter <simona@...ll.ch>
> >> Cc: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>
> >> Cc: Maxime Ripard <mripard@...nel.org>
> >> Cc: Thomas Zimmermann <tzimmermann@...e.de>
> >> Cc: Alexandre Courbot <acourbot@...dia.com>
> >> Cc: Daniel Almeida <daniel.almeida@...labora.com>
> >> Signed-off-by: Danilo Krummrich <dakr@...nel.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@...nel.org>
> >> +M:	Alice Ryhl <aliceryhl@...gle.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?

I guess we would receive just as many patches as we do today :)

> 	@@ -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/

That's not really what I meant, what I meant was that rust/kernel/drm/
is the only thing I'm really interested on, but we don't need to
maintain it if it makes more sense to do so separately.

BTW, we should probably add to drm-misc

X: drivers/gpu/drm/nova

because we have a catch-all at the moment.

Maxime

Download attachment "signature.asc" of type "application/pgp-signature" (274 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ