From: Mark Brown <broonie@kernel•org>
To: "Thomas Hellström" <thomas.hellstrom@linux•intel.com>,
"DRM XE List" <intel-xe@lists•freedesktop.org>,
"Gustavo Sousa" <gustavo.sousa@intel•com>,
"Violet Monti" <violet.monti@intel•com>,
"Matt Roper" <matthew.d.roper@intel•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the drm-xe tree
Date: Wed, 3 Jun 2026 15:02:08 +0100 [thread overview]
Message-ID: <aiAz4DmtngY0r6Cx@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 479 bytes --]
Hi all,
After merging the drm-xe tree, today's linux-next build (x86_64
allmodconfig) failed. Unfortunately I fat fingered things and deleted
the logs, assuming the issue remains I'll report proprely tomorrow. I'm
fairly sure the issue was due to:
5ff004fdc7377 (drm/xe/rtp: Add struct types for RTP tables)
with some of the fields in rtp_to_sr_cases[] haiving non-const values.
Sorry about the lack of clarity here.
I have merged the version from next-20260602 instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-06-03 14:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 14:02 Mark Brown [this message]
2026-06-04 14:35 ` linux-next: build failure after merge of the drm-xe tree Mark Brown
2026-06-04 14:43 ` Thomas Hellström
2026-06-04 14:50 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2026-03-11 13:08 Mark Brown
2026-03-11 17:16 ` Souza, Jose
2026-03-11 18:10 ` Rodrigo Vivi
2026-03-11 18:16 ` Souza, Jose
2026-03-11 20:11 ` Rodrigo Vivi
2026-03-12 7:47 ` Lionel Landwerlin
2026-03-12 11:43 ` Mark Brown
2026-03-13 0:50 ` Rodrigo Vivi
2026-03-13 1:18 ` Souza, Jose
2026-03-13 13:25 ` Mark Brown
2026-03-13 0:46 ` Rodrigo Vivi
2026-03-13 13:57 ` Jani Nikula
2026-03-16 17:38 ` Mark Brown
2026-03-19 8:59 ` Jani Nikula
2026-03-19 9:00 ` Jani Nikula
2025-03-07 2:21 Stephen Rothwell
2025-03-11 2:15 ` Stephen Rothwell
2025-03-07 1:58 Stephen Rothwell
2025-03-11 2:13 ` Stephen Rothwell
2024-12-04 13:36 Mark Brown
2024-12-04 13:46 ` Jani Nikula
2024-12-04 14:18 ` Mark Brown
2024-10-01 1:38 Stephen Rothwell
2024-02-22 8:04 Stephen Rothwell
2024-02-22 17:09 ` Lucas De Marchi
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=aiAz4DmtngY0r6Cx@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=gustavo.sousa@intel$(echo .)com \
--cc=intel-xe@lists$(echo .)freedesktop.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=matthew.d.roper@intel$(echo .)com \
--cc=thomas.hellstrom@linux$(echo .)intel.com \
--cc=violet.monti@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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