From: Besar Wicaksono <bwicaksono@nvidia.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
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>,
Suzuki Poulose <suzuki.poulose@arm.com>
Subject: RE: linux-next: build failure after merge of the arm64 tree
Date: Tue, 15 Nov 2022 23:52:51 +0000 [thread overview]
Message-ID: <SJ0PR12MB56762CFC0B8D680B05828EF8A0049@SJ0PR12MB5676.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20221116090401.0cd5ccc7@canb.auug.org.au>
> -----Original Message-----
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Sent: Tuesday, November 15, 2022 4:04 PM
> To: Catalin Marinas <catalin.marinas@arm.com>; Will Deacon
> <will@kernel.org>
> Cc: Besar Wicaksono <bwicaksono@nvidia.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 arm64 tree
>
> Hi all,
>
> After merging the arm64 tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/perf/arm_cspmu/arm_cspmu.c: In function 'arm_cspmu_get_cpus':
> drivers/perf/arm_cspmu/arm_cspmu.c:1114:29: error: implicit declaration of
> function 'get_acpi_id_for_cpu' [-Werror=implicit-function-declaration]
> 1114 | get_acpi_id_for_cpu(cpu)) {
> | ^~~~~~~~~~~~~~~~~~~
>
+CC Suzuki for awareness.
This function is used for searching CPU with matching ACPI Processor ID in PPTT.
I will check if adding PPTT dependency to arm_cspmu would resolve this issue.
Regards,
Besar
> Caused by commit
>
> e37dfd65731d ("perf: arm_cspmu: Add support for ARM CoreSight PMU
> driver")
>
> I have used the arm64 tree from next-20221115 for today.
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2022-11-15 23:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 22:04 linux-next: build failure after merge of the arm64 tree Stephen Rothwell
2022-11-15 23:52 ` Besar Wicaksono [this message]
2022-11-16 10:49 ` Suzuki K Poulose
-- 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
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=SJ0PR12MB56762CFC0B8D680B05828EF8A0049@SJ0PR12MB5676.namprd12.prod.outlook.com \
--to=bwicaksono@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=suzuki.poulose@arm.com \
--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).