From: Mark Brown <broonie@kernel.org>
To: Juergen Gross <jgross@suse.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Xen Devel <xen-devel@lists.xenproject.org>,
Hou Wenlong <houwenlong.hwl@antgroup.com>,
Alex Deucher <alexdeucher@gmail.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 xen-tip tree
Date: Wed, 4 Mar 2026 14:27:11 +0000 [thread overview]
Message-ID: <aahBPzflrEJ2FPx0@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
Hi all,
After merging the xen-tip tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from /tmp/next/build/drivers/gpu/drm/amd/amdgpu/../display/dc/dc_types.h:38,
from /tmp/next/build/drivers/gpu/drm/amd/amdgpu/../display/dc/dm_services_types.h:30,
from /tmp/next/build/drivers/gpu/drm/amd/amdgpu/../include/dm_pp_interface.h:26,
from /tmp/next/build/drivers/gpu/drm/amd/amdgpu/amdgpu.h:56,
from /tmp/next/build/drivers/gpu/drm/amd/amdgpu/atombios_crtc.c:29:
/tmp/next/build/drivers/gpu/drm/amd/amdgpu/../display/dc/dc_hw_types.h:221:6: error: 'pixel_format' defined as wrong kind of tag
221 | enum pixel_format {
| ^~~~~~~~~~~~
Caused (I think) by commit
4e05a08c6f3f3 (ACPI, x86/boot: Remove {set|get}_root_pointer() ACPI callbacks)
which changes the inclusions and I think triggers namespace clashes with
the unnamespaced pixel_format. I've used the tree from next-20260303
instead but really the fix here is that amdgpu and other things defining
a pixel_format should namespace things, I'll consider if a revert is
more sensible.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-03-04 14:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 14:27 Mark Brown [this message]
2026-03-04 14:37 ` linux-next: build failure after merge of the xen-tip tree Jürgen Groß
-- strict thread matches above, loose matches on Subject: below --
2024-09-12 6:13 Stephen Rothwell
2024-09-12 6:29 ` Jürgen Groß
2024-09-11 6:04 Stephen Rothwell
2021-09-15 1:11 Stephen Rothwell
2018-07-30 5:12 Stephen Rothwell
2018-07-30 7:40 ` Oleksandr Andrushchenko
2018-08-16 0:09 ` Stephen Rothwell
2017-08-31 5:22 Stephen Rothwell
2015-04-13 8:09 Stephen Rothwell
2015-04-13 8:36 ` Bob Liu
2015-04-15 5:00 ` Stephen Rothwell
2015-04-15 10:03 ` David Vrabel
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=aahBPzflrEJ2FPx0@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexdeucher@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=houwenlong.hwl@antgroup.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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