From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Will Deacon <will@kernel.org>
Cc: Ilkka Koskinen <ilkka@os.amperecomputing.com>,
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: Tue, 10 Oct 2023 09:56:01 +1100 [thread overview]
Message-ID: <20231010095601.1443903c@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
Hi all,
After merging the arm-perf tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/perf/arm_cspmu/ampere_cspmu.c: In function 'ampere_cspmu_set_ev_filter':
drivers/perf/arm_cspmu/ampere_cspmu.c:164:9: error: implicit declaration of function 'writel' [-Werror=implicit-function-declaration]
164 | writel(threshold, cspmu->base0 + PMAUXR0);
| ^~~~~~
cc1: all warnings being treated as errors
Caused by commit
290a9c0e55f8 ("perf: arm_cspmu: ampere_cspmu: Add support for Ampere SoC PMU")
I have used the arm-perf tree from next-20231009 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-10-09 22:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 22:56 Stephen Rothwell [this message]
2023-10-10 5:45 ` linux-next: build failure after merge of the arm-perf tree Ilkka Koskinen
2023-10-10 17:50 ` Will Deacon
2023-10-10 18:14 ` Will Deacon
2023-10-10 20:20 ` Ilkka Koskinen
2023-12-12 23:09 Stephen Rothwell
2023-12-13 9:30 ` Will Deacon
2023-12-13 10:15 ` James Clark
2023-12-13 10:56 ` Will Deacon
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=20231010095601.1443903c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ilkka@os.amperecomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).