From: "Arnd Bergmann" <arnd@arndb.de>
To: "Michal Wajdeczko" <michal.wajdeczko@intel.com>,
"Arnd Bergmann" <arnd@kernel.org>,
"Matthew Brost" <matthew.brost@intel.com>,
Thomas Hellström <thomas.hellstrom@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Dave Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
Piotr Piórkowski <piotr.piorkowski@intel.com>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/xe/tests: avoid build warning on 32-bit targets
Date: Wed, 04 Mar 2026 10:06:49 +0100 [thread overview]
Message-ID: <77d07ecc-69d1-4661-b4f8-56a189a3b56b@app.fastmail.com> (raw)
In-Reply-To: <399b1f09-b134-4ec1-bada-5ec053691bf7@intel.com>
On Wed, Mar 4, 2026, at 09:51, Michal Wajdeczko wrote:
> On 3/4/2026 9:37 AM, Arnd Bergmann wrote:
>> From: Arnd Bergmann <arnd@arndb.de>
>> ---
>> If there is a better way to fix this, please treat this as a bug report and
>> just add a Reported-by tag in the commit.
>
> this was already fixed and pushed [1]
>
> [1]
> https://gitlab.freedesktop.org/drm/xe/kernel/-/commit/4f18a79b3585a28c9f73f859fe83f12d0eccc736
>
Right, that looks better than my version. Apparently it just
missed the current linux-next that I was testing on.
Arnd
next prev parent reply other threads:[~2026-03-04 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 8:37 [PATCH] drm/xe/tests: avoid build warning on 32-bit targets Arnd Bergmann
2026-03-04 8:51 ` Michal Wajdeczko
2026-03-04 9:06 ` Arnd Bergmann [this message]
2026-03-05 3:42 ` Claude review: " Claude Code Review Bot
2026-03-05 3:42 ` Claude Code Review Bot
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=77d07ecc-69d1-4661-b4f8-56a189a3b56b@app.fastmail.com \
--to=arnd@arndb.de \
--cc=airlied@gmail.com \
--cc=arnd@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.brost@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=piotr.piorkowski@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