From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Catalin Marinas <catalin.marinas@arm•com>, Will Deacon <will@kernel•org>
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 arm-perf tree
Date: Wed, 13 Dec 2023 10:09:31 +1100 [thread overview]
Message-ID: <20231213100931.12d9d85e@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
Hi all,
After merging the arm-perf tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from drivers/perf/arm_dmc620_pmu.c:26:
include/linux/perf/arm_pmu.h:15:10: fatal error: asm/cputype.h: No such file or directory
15 | #include <asm/cputype.h>
| ^~~~~~~~~~~~~~~
I can't easily tell what caused this - possibly commit
a5f4ca68f348 ("perf/arm_dmc620: Remove duplicate format attribute #defines")
I have used the arm-perf and arm64 trees from next-20231212 for today
(since the arm64 tree merged the arm-perf tree).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-12-12 23:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 23:09 Stephen Rothwell [this message]
2023-12-13 9:30 ` linux-next: build failure after merge of the arm-perf tree Will Deacon
2023-12-13 10:15 ` James Clark
2023-12-13 10:56 ` Will Deacon
-- strict thread matches above, loose matches on Subject: below --
2025-03-17 0:21 Stephen Rothwell
2025-03-17 15:13 ` Will Deacon
2025-03-17 21:23 ` Stephen Rothwell
2023-10-09 22:56 Stephen Rothwell
2023-10-10 5:45 ` Ilkka Koskinen
2023-10-10 17:50 ` Will Deacon
2023-10-10 18:14 ` Will Deacon
2023-10-10 20:20 ` Ilkka Koskinen
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=20231213100931.12d9d85e@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=catalin.marinas@arm$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=will@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