From: Thomas Hellstrom <thomas.hellstrom@linux.intel.com>
To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel.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>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Oded Gabbay" <ogabbay@kernel.org>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
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, 2 May 2024 16:26:21 +0200 [thread overview]
Message-ID: <ZjOijQA43zhu3SZ4@fedora> (raw)
Dave, Sima
This week's small set of fixes for drm-next.
drm-xe-next-fixes-2024-05-02:
Driver Changes:
- Fix for a backmerge going slightly wrong.
- An UAF fix
- Avoid a WA error on LNL.
Thanks,
Thomas
The following changes since commit 4a56c0ed5aa0bcbe1f5f7d755fb1fe1ebf48ae9c:
Merge tag 'amd-drm-next-6.10-2024-04-26' of https://gitlab.freedesktop.org/agd5f/linux into drm-next (2024-04-30 14:43:00 +1000)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/xe/kernel.git tags/drm-xe-next-fixes-2024-05-02
for you to fetch changes up to 3bc8848bb7f7478e6806e4522b06b63f40a53e1e:
drm/xe: Merge 16021540221 and 18034896535 WAs (2024-05-02 11:29:42 +0200)
----------------------------------------------------------------
Driver Changes:
- Fix for a backmerge going slightly wrong.
- An UAF fix
- Avoid a WA error on LNL.
----------------------------------------------------------------
Lucas De Marchi (1):
drm/xe: Merge 16021540221 and 18034896535 WAs
Matthew Auld (1):
drm/xe/vm: prevent UAF in rebind_work_func()
Thomas Hellström (1):
drm/xe: Fix unexpected backmerge results
drivers/gpu/drm/xe/xe_vm.c | 16 ++++++++++------
drivers/gpu/drm/xe/xe_vm_types.h | 4 ++++
drivers/gpu/drm/xe/xe_wa.c | 7 +------
3 files changed, 15 insertions(+), 12 deletions(-)
next reply other threads:[~2024-05-02 14:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 14:26 Thomas Hellstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-19 22:42 [PULL] drm-xe-next-fixes 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-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=ZjOijQA43zhu3SZ4@fedora \
--to=thomas.hellstrom@linux.intel.com \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--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=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ogabbay@kernel.org \
--cc=rodrigo.vivi@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