dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
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 20:09:54 +0200	[thread overview]
Message-ID: <DCIILHRHQ2SP.3MYD6KEP72GV9@kernel.org> (raw)
In-Reply-To: <enuksb2qk5wyrilz3l2vnog45lghgmplrav5to6pd5k5owi36h@pxdq6y5dpgpt>

On Tue Sep 2, 2025 at 7:57 PM CEST, Maxime Ripard wrote:
> 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:
>> > 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.

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. :)

> BTW, we should probably add to drm-misc
>
> X: drivers/gpu/drm/nova

Makes sense.

> because we have a catch-all at the moment.
>
> Maxime


  reply	other threads:[~2025-09-02 18:10 UTC|newest]

Thread overview: 13+ 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
2025-09-02 17:57     ` Maxime Ripard
2025-09-02 18:09       ` Danilo Krummrich [this message]
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

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=DCIILHRHQ2SP.3MYD6KEP72GV9@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).