From: Mark Brown <broonie@kernel•org>
To: Thomas Gleixner <tglx@kernel•org>, Ingo Molnar <mingo@kernel•org>,
"H. Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@infradead•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Josh Snyder <josh@code406•com>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the tip-fixes tree
Date: Wed, 8 Apr 2026 15:50:44 +0100 [thread overview]
Message-ID: <d39364de-70ae-4878-bcd6-1b9497bb394d@sirena.org.uk> (raw)
In-Reply-To: <adZNmIpSOkd6P5c7@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
On Wed, Apr 08, 2026 at 01:44:08PM +0100, Mark Brown wrote:
> After merging the tip-fixes tree, today's linux-next build (arm64 kunit)
> failed like this:
> [12:39:34] [FAILED] <missing>
> [12:39:34] Testing complete. Ran 0 tests: errors: 1
> [12:39:34] Test results stored in /tmp/next/arm64_kunit.json
> [12:39:34] Elapsed time: 316.083s total, 0.002s configuring, 16.074s building, 300.006s running
> which isn't super helpful. I haven't isolated which commit but it'll be
> one of the three:
>
> b81207470caf ("clockevents: Prevent timer interrupt starvation")
It's this one.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-04-08 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 12:44 linux-next: build failure after merge of the tip-fixes tree Mark Brown
2026-04-08 14:50 ` Mark Brown [this message]
2026-04-08 14:54 ` Thomas Weißschuh
2026-04-08 15:21 ` Thomas Gleixner
2026-04-08 15:45 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2025-03-25 23:38 Stephen Rothwell
2025-03-26 1:12 ` Josh Poimboeuf
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=d39364de-70ae-4878-bcd6-1b9497bb394d@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=hpa@zytor$(echo .)com \
--cc=josh@code406$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@kernel$(echo .)org \
--cc=peterz@infradead$(echo .)org \
--cc=tglx@kernel$(echo .)org \
/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