From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Dave Airlie <airlied@gmail.com>, Simona Vetter <simona.vetter@ffwll.ch>
Cc: "Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Matthew Brost" <matthew.brost@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Oded Gabbay" <ogabbay@kernel.org>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, dim-tools@lists.freedesktop.org
Subject: [PULL] drm-xe-next-fixes
Date: Thu, 13 Aug 2026 14:29:47 -0400 [thread overview]
Message-ID: <an4NGzsYN9MOTFII@intel.com> (raw)
Hi Dave and Sima,
Here goes our first drm-xe-next-fixes towards 7.3 with some
small fixes.
Thanks,
Rodrigo.
drm-xe-next-fixes-2026-08-13:
Couple drm-ras fixes, a probe failure clean-up fix, a GT freq
boundaries fixes for BMG/CRI and a Media engines/slice fix.
The following changes since commit 29daacacf4cd84e6917f09de6a99fb170071c14c:
Merge tag 'drm-rust-next-2026-08-08' of https://gitlab.freedesktop.org/drm/rust/kernel into drm-next (2026-08-10 14:48:11 +1000)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/xe/kernel.git tags/drm-xe-next-fixes-2026-08-13
for you to fetch changes up to 1c4d0c45d762539f174cf1d74b2cb21d18e71363:
drm/xe/mcr: Take vcs1/vecs1 into account for first media slice (2026-08-13 09:08:07 -0400)
----------------------------------------------------------------
Couple drm-ras fixes, a probe failure clean-up fix, a GT freq
boundaries fixes for BMG/CRI and a Media engines/slice fix.
----------------------------------------------------------------
Ashutosh Dixit (1):
drm/xe/mcr: Take vcs1/vecs1 into account for first media slice
Raag Jadav (3):
drm/xe/ras: Fix boot-time ras error processing
drm/xe/drm_ras: Move has_drm_ras check to drm_ras layer
drm/xe: Fix xe_device_probe() failure
Vinay Belgaumkar (1):
drm/xe: Fix a bug in pc_adjust_freq_bounds()
drivers/gpu/drm/xe/xe_device.c | 13 ++++++++++++-
drivers/gpu/drm/xe/xe_drm_ras.c | 3 +++
drivers/gpu/drm/xe/xe_gt_mcr.c | 9 +++++++--
drivers/gpu/drm/xe/xe_guc_pc.c | 13 ++++++++++---
drivers/gpu/drm/xe/xe_ras.c | 9 ---------
5 files changed, 32 insertions(+), 15 deletions(-)
next reply other threads:[~2026-08-13 18:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 18:29 Rodrigo Vivi [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-17 19:17 [PULL] drm-xe-next-fixes Matthew Brost
2026-06-17 20:09 ` Matthew Brost
2026-06-21 23:21 ` Dave Airlie
2026-02-19 22:42 Rodrigo Vivi
2026-02-05 14:47 Rodrigo Vivi
2026-01-29 19:19 Rodrigo Vivi
2025-11-21 9:46 Thomas Hellstrom
2025-10-03 20:47 Lucas De Marchi
2025-08-06 13:24 Rodrigo Vivi
2025-07-31 19:46 Rodrigo Vivi
2025-06-05 19:07 Thomas Hellstrom
2025-05-28 16:21 Thomas Hellstrom
2025-05-23 8:25 Thomas Hellstrom
2025-03-27 15:14 Lucas De Marchi
2025-03-13 4:41 Lucas De Marchi
2024-11-28 15:39 Thomas Hellstrom
2024-11-21 19:39 Thomas Hellstrom
2024-11-15 11:10 Thomas Hellstrom
2024-09-20 2:56 Lucas De Marchi
2024-09-20 3:14 ` Lucas De Marchi
2024-09-12 23:23 Lucas De Marchi
2024-07-18 15:51 Rodrigo Vivi
2024-07-09 21:31 Rodrigo Vivi
2024-07-10 19:42 ` Lucas De Marchi
2024-07-10 20:45 ` Rodrigo Vivi
2024-05-09 16:35 Thomas Hellstrom
2024-05-02 14:26 Thomas Hellstrom
2024-03-15 4:14 Lucas De Marchi
2024-03-04 16:00 Lucas De Marchi
2024-01-16 10:22 Thomas Hellström
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=an4NGzsYN9MOTFII@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=mripard@kernel.org \
--cc=ogabbay@kernel.org \
--cc=simona.vetter@ffwll.ch \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tursulin@ursulin.net \
--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