From: Daniel Vetter <daniel@ffwll.ch>
To: Matthew Brost <matthew.brost@intel.com>
Cc: "Luben Tuikov" <ltuikov89@gmail.com>,
dri-devel@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
"Daniel Vetter" <daniel@ffwll.ch>,
"Dave Airlie" <airlied@redhat.com>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH] drm/sched: Add Matthew Brost to maintainers
Date: Wed, 31 Jan 2024 18:11:05 +0100 [thread overview]
Message-ID: <Zbp_KUvsdcSMHsSE@phenom.ffwll.local> (raw)
In-Reply-To: <20240131030302.2088173-1-matthew.brost@intel.com>
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>
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.
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
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2024-01-31 17:12 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 ` Daniel Vetter [this message]
2024-02-01 12:56 ` [PATCH] " Christian König
2024-02-06 0:06 ` Luben Tuikov
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=Zbp_KUvsdcSMHsSE@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@redhat.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=ltuikov89@gmail.com \
--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