From: Jiucheng Xu <jiucheng.xu@amlogic•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Catalin Marinas <catalin.marinas@arm•com>,
Will Deacon <will@kernel•org>
Cc: Chris Healy <healych@amazon•com>,
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: Tue, 22 Nov 2022 12:17:24 +0800 [thread overview]
Message-ID: <e12a12a4-ab6c-ff4a-5cb8-10e498e696a5@amlogic.com> (raw)
In-Reply-To: <20221122104136.601ba45e@canb.auug.org.au>
Hi Stephen,
Could you please share your compiler information, commit id and other
environments info for me to reproduce the building error?
Thanks,
Jiucheng
On 2022/11/22 7:41, Stephen Rothwell wrote:
> Hi all,
>
> After merging the arm64 tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/perf/amlogic/meson_g12_ddr_pmu.c: In function 'dmc_g12_get_freq_quick':
> drivers/perf/amlogic/meson_g12_ddr_pmu.c:135:15: error: implicit declaration of function 'readl' [-Werror=implicit-function-declaration]
> 135 | val = readl(info->pll_reg);
> | ^~~~~
> drivers/perf/amlogic/meson_g12_ddr_pmu.c: In function 'dmc_g12_counter_enable':
> drivers/perf/amlogic/meson_g12_ddr_pmu.c:204:9: error: implicit declaration of function 'writel' [-Werror=implicit-function-declaration]
> 204 | writel(clock_count, info->ddr_reg[0] + DMC_MON_G12_TIMER);
> | ^~~~~~
>
> Caused by commit
>
> 2016e2113d35 ("perf/amlogic: Add support for Amlogic meson G12 SoC DDR PMU driver")
>
> I have used the arm64 tree from next-20221121 for today.
>
--
Thanks,
Jiucheng
next prev parent reply other threads:[~2022-11-22 4:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 23:41 linux-next: build failure after merge of the arm64 tree Stephen Rothwell
2022-11-22 4:17 ` Jiucheng Xu [this message]
2022-11-22 4:52 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
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=e12a12a4-ab6c-ff4a-5cb8-10e498e696a5@amlogic.com \
--to=jiucheng.xu@amlogic$(echo .)com \
--cc=catalin.marinas@arm$(echo .)com \
--cc=healych@amazon$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--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