From: Thomas Hellstrom <thomas.hellstrom@linux.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>,
"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] topic/xe-vfio for 6.19
Date: Thu, 4 Dec 2025 22:45:26 +0100 [thread overview]
Message-ID: <aTIA9in2Bo_fA9TN@fedora> (raw)
Hi Dave, Simona
Please consider pulling this fix and (as a prereq) the original pull-request
https://lore.kernel.org/dri-devel/aS1bNpqeem6PIHrA@fedora/
for 6.19 as discussed on IRC.
topic/xe-vfio-2025-12-04:
Driver Changes:
- fix VFIO link error for built-in xe module (Arnd Bergmann)
The following changes since commit 1f5556ec8b9efbb784aeb3536e147182dee73d0f:
vfio/xe: Add device specific vfio_pci driver variant for Intel graphics (2025-12-01 09:45:48 +0100)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/xe/kernel.git tags/topic/xe-vfio-2025-12-04
for you to fetch changes up to e45b5df47b07e6ce1138b0a4e70ad0b0c4d72881:
drm/xe/pf: fix VFIO link error (2025-12-04 16:34:00 +0100)
----------------------------------------------------------------
Driver Changes:
- fix VFIO link error for built-in xe module (Arnd Bergmann)
----------------------------------------------------------------
Arnd Bergmann (1):
drm/xe/pf: fix VFIO link error
drivers/gpu/drm/xe/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
reply other threads:[~2025-12-04 21:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aTIA9in2Bo_fA9TN@fedora \
--to=thomas.hellstrom@linux.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=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ogabbay@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona.vetter@ffwll.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.