From: "Arnd Bergmann" <arnd@arndb.de>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Arnd Bergmann" <arnd@kernel.org>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Dave Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Michał Winiarski" <michal.winiarski@intel.com>,
"Michal Wajdeczko" <michal.wajdeczko@intel.com>
Cc: "Matthew Brost" <matthew.brost@intel.com>,
"Lucas De Marchi" <demarchi@kernel.org>,
"Jani Nikula" <jani.nikula@intel.com>,
"Riana Tauro" <riana.tauro@intel.com>,
intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/xe/pf: fix VFIO link error
Date: Thu, 04 Dec 2025 14:43:00 +0100 [thread overview]
Message-ID: <079b5829-1ebd-4df8-873c-b75625a52fac@app.fastmail.com> (raw)
In-Reply-To: <c174c12d9748e2e9b2e497c1e479100c323e79c2.camel@linux.intel.com>
On Thu, Dec 4, 2025, at 13:19, Thomas Hellström wrote:
> On Thu, 2025-12-04 at 10:41 +0100, Arnd Bergmann wrote:
>>
>> Check for CONFIG_XE_VFIO_PCI being enabled in the Makefile to decide
>> whether to
>> include the the object instead.
>
> s/the the/the/ found by CI.
> Same question here, Do you want to resent or should I fix up when
> commiting?
>
I'd prefer if you can fix up both so I don't have to send it again.
Arnd
next prev parent reply other threads:[~2025-12-04 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 9:41 [PATCH] drm/xe/pf: fix VFIO link error Arnd Bergmann
2025-12-04 9:46 ` ✗ CI.checkpatch: warning for " Patchwork
2025-12-04 9:48 ` ✓ CI.KUnit: success " Patchwork
2025-12-04 11:08 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-04 12:10 ` [PATCH] " Michal Wajdeczko
2025-12-04 12:19 ` Thomas Hellström
2025-12-04 13:43 ` Arnd Bergmann [this message]
2025-12-04 13:44 ` Thomas Hellström
2025-12-04 12:22 ` ✓ Xe.CI.Full: success for " 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=079b5829-1ebd-4df8-873c-b75625a52fac@app.fastmail.com \
--to=arnd@arndb.de \
--cc=airlied@gmail.com \
--cc=arnd@kernel.org \
--cc=demarchi@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.brost@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=michal.winiarski@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=thomas.hellstrom@linux.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