From: Will Deacon <will@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <maz@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
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 arm64 tree
Date: Wed, 24 Jun 2026 14:05:21 +0100 [thread overview]
Message-ID: <ajvWESo4ybnDRyVG@willie-the-truck> (raw)
In-Reply-To: <ajvGS7UBpWzJtzkw@sirena.org.uk>
On Wed, Jun 24, 2026 at 12:58:03PM +0100, Mark Brown wrote:
> Hi all,
>
> After merging the arm64 tree, today's linux-next build
> (arm64 kselftest) failed like this:
>
> CC iommufd_fail_nth
> CC iommufd
> CC msgque
> CC ir_loopback
> CC kcmp_test
> CC harness-selftest
> In file included from /usr/include/aarch64-linux-gnu/bits/sigcontext.h:30,
> from /usr/include/signal.h:301,
> from include/test_util.h:12,
> from lib/io.c:8:
> /tmp/next/arm64_kselftest/usr/include/asm/sigcontext.h:81:9: error:
> unknown type name '__u128'; did you mean '__u32'?
> 81 | __u128 vregs[32];
> | ^~~~~~ __u32
> cc1: note: unrecognized command-line option
> '-Wno-gnu-variable-sized-type-not-at-end' may have been intended
> to silence earlier diagnostics make[1]: *** [Makefile.kvm:347:
> /tmp/next/arm64_kselftest/kselftest/kvm/lib/io.o] Error 1 make[1]:
Thanks, Mark. I also got a similar report from test robot [1], so I'll
just drop this change until I've figured out the root cause.
Will
[1] https://lore.kernel.org/r/202606240441.7eZ1TIRM-lkp@intel.com
next prev parent reply other threads:[~2026-06-24 13:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 11:58 linux-next: build failure after merge of the arm64 tree Mark Brown
2026-06-24 13:05 ` Will Deacon [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-21 23:41 Stephen Rothwell
2022-11-22 4:17 ` Jiucheng Xu
2022-11-22 4:52 ` Stephen Rothwell
2022-11-15 22:04 Stephen Rothwell
2022-11-15 23:52 ` Besar Wicaksono
2022-11-16 10:49 ` Suzuki K Poulose
2019-08-06 23:50 Stephen Rothwell
2019-08-07 2:34 ` Peter Collingbourne
2019-08-07 11:46 ` Will Deacon
2019-08-07 14:43 ` Masahiro Yamada
2019-08-07 15:25 ` Will Deacon
2019-08-07 16:33 ` Peter Collingbourne
2019-08-07 23:43 ` Stephen Rothwell
2019-08-16 4:52 ` Michael Ellerman
2019-08-16 17:27 ` Will Deacon
2019-08-20 7:27 ` Michael Ellerman
2015-03-27 0:15 Stephen Rothwell
2012-09-17 1:24 Stephen Rothwell
2012-09-17 8:41 ` Catalin Marinas
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=ajvWESo4ybnDRyVG@willie-the-truck \
--to=will@kernel.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.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