From: Mark Brown <broonie@kernel.org>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: 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>,
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, 4 Jun 2026 15:50:24 +0100 [thread overview]
Message-ID: <551d384f-d151-4d1e-bcb8-a1cde0860a30@sirena.org.uk> (raw)
In-Reply-To: <f9094757b2aab617feb8fc3f8a66f46595e0ae27.camel@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 853 bytes --]
On Thu, Jun 04, 2026 at 04:43:17PM +0200, Thomas Hellström wrote:
> On Thu, 2026-06-04 at 15:35 +0100, Mark Brown wrote:
> > /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);}))
> 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?
This is after merging the tree into -next, that'd be on top of
09b893db4d9e68c2679e76624d420f438f8d3e98 for today (not published yet).
It's possible it's some interaction with other trees (like the main drm
tree) and works as a standalone thing, it wasn't obviously that from a
quick investigation. The toolchain is gcc from Debian stable.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-06-04 14:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 14:02 Mark Brown
2026-06-04 14:35 ` Mark Brown
2026-06-04 14:43 ` Thomas Hellström
2026-06-04 14:50 ` Mark Brown [this message]
2026-06-04 17:23 ` Thomas Hellström
2026-06-05 6:03 ` Nathan Chancellor
2026-06-05 11:08 ` 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=551d384f-d151-4d1e-bcb8-a1cde0860a30@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gustavo.sousa@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=matthew.d.roper@intel.com \
--cc=thomas.hellstrom@linux.intel.com \
--cc=violet.monti@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
all inboxes | Powered by JetHome®