From: Lucas De Marchi <lucas.demarchi@intel.com>
To: <intel-xe@lists.freedesktop.org>
Cc: dri-devel@lists.freedesktop.org,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Lucas De Marchi" <lucas.demarchi@intel.com>
Subject: [PATCH] MAINTAINERS: Also exclude xe for drm-misc
Date: Fri, 17 Jan 2025 08:45:29 -0800 [thread overview]
Message-ID: <20250117164529.393503-1-lucas.demarchi@intel.com> (raw)
When the xe driver was added, it didn't extend the exclude entries for
drm-misc, as done in commit 5a44d50f0072 ("MAINTAINERS: Update drm-misc
entry to match all drivers"). Exclude it like is done for i915 and other
drivers with dedicated maintainers.
Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index d32d0a9428234..30d8e47a0e5f3 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7606,6 +7606,7 @@ X: drivers/gpu/drm/nouveau/
X: drivers/gpu/drm/radeon/
X: drivers/gpu/drm/renesas/rcar-du/
X: drivers/gpu/drm/tegra/
+X: drivers/gpu/drm/xe/
DRM DRIVERS FOR ALLWINNER A10
M: Maxime Ripard <mripard@kernel.org>
--
2.48.0
next reply other threads:[~2025-01-17 16:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 16:45 Lucas De Marchi [this message]
2025-01-17 17:22 ` ✓ CI.Patch_applied: success for MAINTAINERS: Also exclude xe for drm-misc Patchwork
2025-01-17 17:22 ` ✓ CI.checkpatch: " Patchwork
2025-01-17 17:23 ` ✓ CI.KUnit: " Patchwork
2025-01-17 17:41 ` ✓ CI.Build: " Patchwork
2025-01-17 17:42 ` [PATCH] " Rodrigo Vivi
2025-01-21 23:19 ` Lucas De Marchi
2025-01-17 17:44 ` ✓ CI.Hooks: success for " Patchwork
2025-01-17 17:45 ` ✓ CI.checksparse: " Patchwork
2025-01-20 6:06 ` ✓ Xe.CI.BAT: " Patchwork
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=20250117164529.393503-1-lucas.demarchi@intel.com \
--to=lucas.demarchi@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=thomas.hellstrom@linux.intel.com \
--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