From: "Thomas Hellström" <thomas.hellstrom@linux•intel.com>
To: Mark Brown <broonie@kernel•org>,
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: Re: linux-next: build failure after merge of the drm-xe tree
Date: Thu, 04 Jun 2026 16:43:17 +0200 [thread overview]
Message-ID: <f9094757b2aab617feb8fc3f8a66f46595e0ae27.camel@linux.intel.com> (raw)
In-Reply-To: <bfb0dee8-b243-47ba-a89d-71472b0d51c5@sirena.org.uk>
On Thu, 2026-06-04 at 15:35 +0100, Mark Brown wrote:
> On Wed, Jun 03, 2026 at 03:02:08PM +0100, Mark Brown wrote:
> > 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.
>
> The error message is:
>
> /tmp/next/build/drivers/gpu/drm/xe/xe_hw_engine.c:361:6: error:
> initializer element is not a compile-time constant
> 361 | blit_cctl_val,
> | ^~~~~~~~~~~~~
> /tmp/next/build/drivers/gpu/drm/xe/xe_rtp.h:461:41: note: expanded
> from macro 'XE_RTP_ACTIONS'
> 461 | XE_RTP_PASTE_FOREACH(ACTION_, COMMA,
> (__VA_ARGS__)) \
> |
> ^~~~~~~~~~~
> /tmp/next/build/drivers/gpu/drm/xe/xe_rtp_helpers.h:56:108: note:
> expanded from macro 'XE_RTP_PASTE_FOREACH'
> 56 | #define XE_RTP_PASTE_FOREACH(prefix_, sep_, args_)
> _XE_RTP_CONCAT(PASTE_, COUNT_ARGS args_)(prefix_, sep_, args_)
>
> |
> ^~~~~
> /tmp/next/build/drivers/gpu/drm/xe/xe_rtp_helpers.h:57:80: note:
> expanded from macro 'XE_RTP_PASTE_1'
> 57 | #define XE_RTP_PASTE_1(prefix_, sep_, args_)
> _XE_RTP_CONCAT(prefix_, FIRST_ARG args_)
>
> |
> ^~~~~
> note: (skipping 11 expansions in backtrace; use -fmacro-backtrace-
> limit=0 to see all)
> /tmp/next/build/include/linux/compiler.h:204:39: note: expanded from
> macro '__is_array'
> 204 | #define __is_array(a) (!__same_type((a), &(a)[0]))
> | ^
> /tmp/next/build/include/linux/compiler_types.h:610:63: note: expanded
> from macro '__same_type'
> 610 | #define __same_type(a, b)
> __builtin_types_compatible_p(typeof(a), typeof(b))
> |
> ^
> /tmp/next/build/include/linux/compiler.h:200:84: note: expanded from
> macro '__BUILD_BUG_ON_ZERO_MSG'
> 200 | #define __BUILD_BUG_ON_ZERO_MSG(e, msg, ...)
> ((int)sizeof(struct {_Static_assert(!(e), msg);}))
>
> |
> ^
> /tmp/next/build/drivers/gpu/drm/xe/xe_hw_engine.c:416:9: error:
> initializer element is not a compile-time constant
> 416 | ring_cmd_cctl_val,
> | ^~~~~~~~~~~~~~~~~
> /tmp/next/build/drivers/gpu/drm/xe/xe_rtp.h:461:41: note: expanded
> from macro 'XE_RTP_ACTIONS'
> 461 | XE_RTP_PASTE_FOREACH(ACTION_, COMMA,
> (__VA_ARGS__)) \
> |
> ^~~~~~~~~~~
> /tmp/next/build/drivers/gpu/drm/xe/xe_rtp_helpers.h:56:108: note:
> expanded from macro 'XE_RTP_PASTE_FOREACH'
> 56 | #define XE_RTP_PASTE_FOREACH(prefix_, sep_, args_)
> _XE_RTP_CONCAT(PASTE_, COUNT_ARGS args_)(prefix_, sep_, args_)
>
> |
> ^~~~~
> /tmp/next/build/drivers/gpu/drm/xe/xe_rtp_helpers.h:57:80: note:
> expanded from macro 'XE_RTP_PASTE_1'
> 57 | #define XE_RTP_PASTE_1(prefix_, sep_, args_)
> _XE_RTP_CONCAT(prefix_, FIRST_ARG args_)
>
> |
> ^~~~~
> note: (skipping 11 expansions in backtrace; use -fmacro-backtrace-
> limit=0 to see all)
> /tmp/next/build/include/linux/compiler.h:204:39: note: expanded from
> macro '__is_array'
> 204 | #define __is_array(a) (!__same_type((a), &(a)[0]))
> | ^
> /tmp/next/build/include/linux/compiler_types.h:610:63: note: expanded
> from macro '__same_type'
> 610 | #define __same_type(a, b)
> __builtin_types_compatible_p(typeof(a), typeof(b))
> |
> ^
> /tmp/next/build/include/linux/compiler.h:200:84: note: expanded from
> macro '__BUILD_BUG_ON_ZERO_MSG'
> 200 | #define __BUILD_BUG_ON_ZERO_MSG(e, msg, ...)
> ((int)sizeof(struct {_Static_assert(!(e), msg);}))
>
> |
> ^
> 2 errors generated.
Funny, I see no build errors with drm-xe-next allmodconfig. What
compiler is being used? Any sha1 of the drm-xe-next top commit you're
testing?
Thanks,
Thomas
next prev parent reply other threads:[~2026-06-04 14:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 14:02 linux-next: build failure after merge of the drm-xe tree Mark Brown
2026-06-04 14:35 ` Mark Brown
2026-06-04 14:43 ` Thomas Hellström [this message]
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=f9094757b2aab617feb8fc3f8a66f46595e0ae27.camel@linux.intel.com \
--to=thomas.hellstrom@linux$(echo .)intel.com \
--cc=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=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