From: Danilo Krummrich <dakr@kernel.org>
To: Alice Ryhl <aliceryhl@google.com>
Cc: airlied@gmail.com, simona@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
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,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH] MAINTAINERS: Add drm-rust tree for Rust DRM drivers and infrastructure
Date: Thu, 4 Sep 2025 13:09:45 +0200 [thread overview]
Message-ID: <08632fbd-1984-44ff-a6e1-bd9e39bbea97@kernel.org> (raw)
In-Reply-To: <aLlsmNzp_KardLUt@google.com>
(Cc: Jani)
On 9/4/25 12:40 PM, Alice Ryhl wrote:
> On Mon, Sep 01, 2025 at 10:26:39PM +0200, Danilo Krummrich wrote:
>> +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
>
> It 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.
next prev parent reply other threads:[~2025-09-04 11:09 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
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 [this message]
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=08632fbd-1984-44ff-a6e1-bd9e39bbea97@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=jani.nikula@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.