From: Luben Tuikov <ltuikov89@gmail.com>
To: "Christian König" <christian.koenig@amd.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Matthew Brost" <matthew.brost@intel.com>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Dave Airlie <airlied@redhat.com>
Subject: Re: [PATCH] drm/sched: Add Matthew Brost to maintainers
Date: Mon, 5 Feb 2024 19:06:45 -0500 [thread overview]
Message-ID: <658318d1-25e9-48f0-9e36-9923f38fa431@gmail.com> (raw)
In-Reply-To: <9dac66fd-2d84-488e-93f5-3983cd13d0bd@amd.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1823 bytes --]
On 2024-02-01 07:56, Christian König wrote:
> Am 31.01.24 um 18:11 schrieb Daniel Vetter:
>> On Tue, Jan 30, 2024 at 07:03:02PM -0800, Matthew Brost wrote:
>>> Add Matthew Brost to DRM scheduler maintainers.
>>>
>>> Cc: Luben Tuikov <ltuikov89@gmail.com>
>>> Cc: Daniel Vetter <daniel@ffwll.ch>
>>> Cc: Dave Airlie <airlied@redhat.com>
>>> Cc: Christian König <christian.koenig@amd.com>
>>> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
>> Definitely need more people taking care of drm/sched, so thanks for
>> volunteering!
>>
>> Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Yeah, that's a good idea.
Acked-by: Luben Tuikov <ltuikov89@gmail.com>
Regards,
Luben
>>
>> I think this also needs an ack from Luben and Christian. And you also need
>> drm-misc commit rights first, or it's going to be a bit tricky to take
>> care of maintainer duties for merging patches. But since your sched
>> patches now have landed in upstream this should be just a formality.
>
> Ack from my side, I don't have time to look into scheduler stuff anyway.
>
> Maybe I can get somebody from Leo's team to volunteer as another
> reviewer for scheduler related stuff.
>
> Cheers,
> Christian.
>
>>
>> Cheers, Sima
>>
>>> ---
>>> MAINTAINERS | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index 5c00fad59e91..e968d68a96c8 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -7308,6 +7308,7 @@ F: drivers/gpu/drm/xlnx/
>>>
>>> DRM GPU SCHEDULER
>>> M: Luben Tuikov <ltuikov89@gmail.com>
>>> +M: Matthew Brost <matthew.brost@intel.com>
>>> L: dri-devel@lists.freedesktop.org
>>> S: Maintained
>>> T: git git://anongit.freedesktop.org/drm/drm-misc
>>> --
>>> 2.34.1
>>>
>
--
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 --]
next prev parent reply other threads:[~2024-02-06 0:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 3:03 [PATCH] drm/sched: Add Matthew Brost to maintainers Matthew Brost
2024-01-31 6:01 ` ✓ CI.Patch_applied: success for " Patchwork
2024-01-31 6:01 ` ✓ CI.checkpatch: " Patchwork
2024-01-31 6:02 ` ✓ CI.KUnit: " Patchwork
2024-01-31 6:09 ` ✓ CI.Build: " Patchwork
2024-01-31 6:10 ` ✓ CI.Hooks: " Patchwork
2024-01-31 6:11 ` ✓ CI.checksparse: " Patchwork
2024-01-31 6:55 ` ✓ CI.BAT: " Patchwork
2024-01-31 17:11 ` [PATCH] " Daniel Vetter
2024-02-01 12:56 ` Christian König
2024-02-06 0:06 ` Luben Tuikov [this message]
2024-02-06 0:23 ` Luben Tuikov
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=658318d1-25e9-48f0-9e36-9923f38fa431@gmail.com \
--to=ltuikov89@gmail.com \
--cc=airlied@redhat.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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