From: Luben Tuikov <ltuikov89@gmail.com>
To: Danilo Krummrich <dakr@kernel.org>,
"Cavitt, Jonathan" <jonathan.cavitt@intel.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Gupta, Saurabhg" <saurabhg.gupta@intel.com>,
"Zuo, Alex" <alex.zuo@intel.com>,
"Brost, Matthew" <matthew.brost@intel.com>,
"thomas.hellstrom@linux.intel.com"
<thomas.hellstrom@linux.intel.com>,
"aliceryhl@google.com" <aliceryhl@google.com>,
dri-devel <dri-devel-bounces@lists.freedesktop.org>
Subject: Re: [PATCH] drm/gpuvm: Do not prepare NULL objects
Date: Fri, 17 Apr 2026 00:20:54 -0400 [thread overview]
Message-ID: <bf14d241-1505-4082-980f-e43ef20ea13d@gmail.com> (raw)
In-Reply-To: <DHUVF2NYOGWV.2DQ3FJIPDF4B1@kernel.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 1523 bytes --]
On 2026-04-16 16:44, Danilo Krummrich wrote:
> On Thu Apr 16, 2026 at 10:23 PM CEST, Jonathan Cavitt wrote:
>> Question for the future:
>> Is Lankhorst, Maarten a proper maintainer for this component?
>
> Maarten is one of the drm-misc tree maintainers.
>
> DRM is a bit special in this regard compared to other kernel subsystems, as DRM
> also allows non-maintainers to push to development trees. Yet, those development
> trees still need to be run by someone and those people are the tree maintainers.
>
> Additionally, there are people maintaining the individual components, drivers,
> etc. and those are usually the people with the strongest domain knowledge.
>
> Patches should be sent to both the tree maintainers and the component
> maintainers.
>
>> If not, is there a list I can reference to determine who the proper
>> maintainers I should be contacting are?
>
> Absolutely, everything is documented in the MAINTAINERS file in the kernel tree.
>
> The best way to figure out who to send patches to is to use
> ./scripts/get_maintainer.pl. The script should provide you with the full list of
> all relevant maintainers and reviewers for your patch.
>
> Additionally, it also outputs people who have been involved in the corresponding
> component and may be worth Cc'ing as well.
>
> If you run it for your patch you should get the output below.
>
> I hope this helps!
That's a great response! Indeed, the get_maintainer.pl is a good tool to use.
--
Regards,
Luben
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 677 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2026-04-17 4:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 19:19 [PATCH] drm/gpuvm: Do not prepare NULL objects Jonathan Cavitt
2026-02-24 15:41 ` Krzysztof Karas
2026-04-16 20:01 ` Danilo Krummrich
2026-04-16 20:23 ` Cavitt, Jonathan
2026-04-16 20:44 ` Danilo Krummrich
2026-04-17 4:20 ` Luben Tuikov [this message]
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=bf14d241-1505-4082-980f-e43ef20ea13d@gmail.com \
--to=ltuikov89@gmail.com \
--cc=alex.zuo@intel.com \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=dri-devel-bounces@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=matthew.brost@intel.com \
--cc=saurabhg.gupta@intel.com \
--cc=thomas.hellstrom@linux.intel.com \
/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