MAINTAINERS: Add drm-rust tree for Rust DRM drivers and infrastructure
Danilo Krummrich
reviewerPATCH 1/1 MAINTAINERS: Add drm-rust tree for Rust DRM drivers and infrastructure
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.
--- MAINTAINERS | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-)
MAINTAINERS +10 -1
@@ -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 <[email protected]> +M: Alice Ryhl <[email protected]> +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/ + DRM DRIVERS FOR ALLWINNER A10 M: Maxime Ripard <[email protected]> M: Chen-Yu Tsai <[email protected]>
base-commit: 8f5ae30d69d7543eee0d70083daf4de8fe15d585
Signature · 1 line
2.51.0
Quoted 23 lines · Danilo Krummrich
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.
Quoted 9 lines
Cc Alice Ryhl <[email protected]>Cc David Airlie <[email protected]>Cc Simona Vetter <[email protected]>Cc Maarten Lankhorst <[email protected]>Cc Maxime Ripard <[email protected]>Cc Thomas Zimmermann <[email protected]>Cc Alexandre Courbot <[email protected]>Cc Daniel Almeida <[email protected]>Signed-off-by Danilo Krummrich <[email protected]>
Quoted 70 lines · Danilo Krummrich
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 <[email protected]>Cc David Airlie <[email protected]>Cc Simona Vetter <[email protected]>Cc Maarten Lankhorst <[email protected]>Cc Maxime Ripard <[email protected]>Cc Thomas Zimmermann <[email protected]>Cc Alexandre Courbot <[email protected]>Cc Daniel Almeida <[email protected]>Signed-off-by Danilo Krummrich <[email protected]>---
MAINTAINERS| 11 ++++++++++-1 file changed, 10 insertions(+), 1 deletion(-)MAINTAINERS +0
-0@@ -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/MAINTAINERS +0
-0@@ -8096,6 +8095,16 @@ X: drivers/gpu/drm/radeon/X:
drivers/gpu/drm/tegra/
X:drivers/gpu/drm/xe/MAINTAINERS +10
-0+DRM DRIVERS AND COMMON INFRASTRUCTURE [RUST] +M: Danilo Krummrich <[email protected]> +M: Alice Ryhl <[email protected]> +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/ +DRM DRIVERS FOR ALLWINNER A10
M: Maxime Ripard <[email protected]>
M: Chen-Yu Tsai <[email protected]>
Quoted 4 lines
base-commit:
8f5ae30d69d7543eee0d70083daf4de8fe15d585Signature · 1 line
2.51.0
Quoted 23 lines · Danilo Krummrich
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.
Quoted 9 lines
Cc Alice Ryhl <[email protected]>Cc David Airlie <[email protected]>Cc Simona Vetter <[email protected]>Cc Maarten Lankhorst <[email protected]>Cc Maxime Ripard <[email protected]>Cc Thomas Zimmermann <[email protected]>Cc Alexandre Courbot <[email protected]>Cc Daniel Almeida <[email protected]>Signed-off-by Danilo Krummrich <[email protected]>
FWIW,
Quoted 35 lines
--- MAINTAINERS | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-)MAINTAINERS +10
-1@@ -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 <[email protected]> +M: Alice Ryhl <[email protected]> +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/ + DRM DRIVERS FOR ALLWINNER A10 M: Maxime Ripard <[email protected]> M: Chen-Yu Tsai <[email protected]>base-commit:
8f5ae30d69d7543eee0d70083daf4de8fe15d585
Signature · 1 line
Jani Nikula, Intel
Quoted 23 lines · Danilo Krummrich
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.
Quoted 9 lines
Cc Alice Ryhl <[email protected]>Cc David Airlie <[email protected]>Cc Simona Vetter <[email protected]>Cc Maarten Lankhorst <[email protected]>Cc Maxime Ripard <[email protected]>Cc Thomas Zimmermann <[email protected]>Cc Alexandre Courbot <[email protected]>Cc Daniel Almeida <[email protected]>Signed-off-by Danilo Krummrich <[email protected]>
Quoted 52 lines · Danilo Krummrich
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 <[email protected]>Cc David Airlie <[email protected]>Cc Simona Vetter <[email protected]>Cc Maarten Lankhorst <[email protected]>Cc Maxime Ripard <[email protected]>Cc Thomas Zimmermann <[email protected]>Cc Alexandre Courbot <[email protected]>Cc Daniel Almeida <[email protected]>Signed-off-by Danilo Krummrich <[email protected]>--- MAINTAINERS | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-)MAINTAINERS +0
-1@@ -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/
MAINTAINERS X: drivers/gpu/drm/radeon/ · line 8107
Quoted 10 lines
MAINTAINERS +10
-0+DRM DRIVERS AND COMMON INFRASTRUCTURE [RUST] +M: Danilo Krummrich <[email protected]> +M: Alice Ryhl <[email protected]> +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?
Either way,
Maxime
Danilo Krummrich
reviewerQuoted 53 lines · Maxime Ripard
Quoted 52 lines · Danilo Krummrich
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 <[email protected]>Cc David Airlie <[email protected]>Cc Simona Vetter <[email protected]>Cc Maarten Lankhorst <[email protected]>Cc Maxime Ripard <[email protected]>Cc Thomas Zimmermann <[email protected]>Cc Alexandre Courbot <[email protected]>Cc Daniel Almeida <[email protected]>Signed-off-by Danilo Krummrich <[email protected]>--- MAINTAINERS | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-)MAINTAINERS +0
-1@@ -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/
Quoted 13 lines
MAINTAINERS X: drivers/gpu/drm/radeon/ · line 8107
Quoted 10 lines
MAINTAINERS +10
-0+DRM DRIVERS AND COMMON INFRASTRUCTURE [RUST] +M: Danilo Krummrich <[email protected]> +M: Alice Ryhl <[email protected]> +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/
Quoted 5 lines
Either way,
Acked-by Maxime Ripard <[email protected]>Maxime
Quoted 68 lines · Danilo Krummrich
Quoted 53 lines · Maxime Ripard
Quoted 52 lines · Danilo Krummrich
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 <[email protected]>Cc David Airlie <[email protected]>Cc Simona Vetter <[email protected]>Cc Maarten Lankhorst <[email protected]>Cc Maxime Ripard <[email protected]>Cc Thomas Zimmermann <[email protected]>Cc Alexandre Courbot <[email protected]>Cc Daniel Almeida <[email protected]>Signed-off-by Danilo Krummrich <[email protected]>--- MAINTAINERS | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-)MAINTAINERS +0
-1@@ -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/Quoted 13 lines
MAINTAINERS X: drivers/gpu/drm/radeon/ · line 8107
Quoted 10 lines
MAINTAINERS +10
-0+DRM DRIVERS AND COMMON INFRASTRUCTURE [RUST] +M: Danilo Krummrich <[email protected]> +M: Alice Ryhl <[email protected]> +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?
Quoted 2 lines
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 :)
Quoted 8 lines
@@ -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
Danilo Krummrich
reviewerQuoted 19 lines · Maxime Ripard
Quoted 6 lines · Danilo Krummrich
Quoted 2 lines · Maxime Ripard
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 :)
Quoted 8 lines
@@ -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/
Quoted 3 lines
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.
Yeah, the idea was to discard the hunk above and still keep rust/kernel/drm/ on this new entry, so you get *only* that, but not all the driver patches.
As far as file maintainership is concerned, we have group maintainership on the commmon infrastructure anyways.
Your call, happy to add you as reviewers to the new entry too. :)
Quoted 3 lines
BTW, we should probably add to drm-misc
X:
drivers/gpu/drm/nova
Makes sense.
Quoted 3 lines
because we have a catch-all at the moment.
Maxime
Hej,
Quoted 17 lines · Danilo Krummrich
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.
Quoted 5 lines
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.
I think this good idea. I plan to make an initial asahi submission based on v6.18-rc1. Feel free to add asahi to the list.
Alice Ryhl
reviewerQuoted 49 lines · Danilo Krummrich
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 <[email protected]>Cc David Airlie <[email protected]>Cc Simona Vetter <[email protected]>Cc Maarten Lankhorst <[email protected]>Cc Maxime Ripard <[email protected]>Cc Thomas Zimmermann <[email protected]>Cc Alexandre Courbot <[email protected]>Cc Daniel Almeida <[email protected]>Signed-off-by Danilo Krummrich <[email protected]>--- MAINTAINERS | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-)MAINTAINERS +0
-1@@ -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/
MAINTAINERS X: drivers/gpu/drm/radeon/ · line 8102
Quoted 8 lines
MAINTAINERS +5
-0@@ -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 <[email protected]> +M: Alice Ryhl <[email protected]> +S: Supported +W: https://drm.pages.freedesktop.org/maintainer-tools/drm-rust.html
It looks like the right path is:
https://drm.pages.freedesktop.org/maintainer-tools/repositories/drm-rust.html
Alice
Danilo Krummrich
reviewer(Cc: Jani)
Quoted 9 lines · Alice Ryhl
MAINTAINERS X: drivers/gpu/drm/radeon/ · line 8102
Quoted 5 lines · Danilo Krummrich
MAINTAINERS +5
-0+DRM DRIVERS AND COMMON INFRASTRUCTURE [RUST] +M: Danilo Krummrich <[email protected]> +M: Alice Ryhl <[email protected]> +S: Supported +W: https://drm.pages.freedesktop.org/maintainer-tools/drm-rust.htmlIt looks like the right path is:
https://drm.pages.freedesktop.org/maintainer-tools/repositories/drm-rust.html
Heh, seems like there's an explicit redirect for drm-misc:
https://drm.pages.freedesktop.org/maintainer-tools/drm-misc.html
I think we should get the same redirect, so the links in MAINTAINERS are consistent with each other.
Danilo Krummrich
reviewerQuoted 2 lines · Danilo Krummrich
I think we should get the same redirect, so the links in
MAINTAINERSare consistent with each other.
https://gitlab.freedesktop.org/drm/maintainer-tools/-/merge_requests/89
Quoted 23 lines · Danilo Krummrich
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.
Quoted 9 lines
Cc Alice Ryhl <[email protected]>Cc David Airlie <[email protected]>Cc Simona Vetter <[email protected]>Cc Maarten Lankhorst <[email protected]>Cc Maxime Ripard <[email protected]>Cc Thomas Zimmermann <[email protected]>Cc Alexandre Courbot <[email protected]>Cc Daniel Almeida <[email protected]>Signed-off-by Danilo Krummrich <[email protected]>
Applied to drm-rust-fixes. Thanks!