From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jiucheng Xu <jiucheng.xu@amlogic.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, 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 15:52:16 +1100 [thread overview]
Message-ID: <20221122155216.47e0aca9@canb.auug.org.au> (raw)
In-Reply-To: <e12a12a4-ab6c-ff4a-5cb8-10e498e696a5@amlogic.com>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
Hi,
On Tue, 22 Nov 2022 12:17:24 +0800 Jiucheng Xu <jiucheng.xu@amlogic.com> wrote:
>
> Could you please share your compiler information, commit id and other
>
> environments info for me to reproduce the building error?
$ x86_64-linux-gnu-gcc --version
x86_64-linux-gnu-gcc (Debian 12.2.0-3) 12.2.0
The head of the arm64 tree that I merged was
27131b99f024 ("Merge branches 'for-next/acpi', 'for-next/asm-const', 'for-next/cpufeature', 'for-next/dynamic-scs', 'for-next/errata', 'for-next/fpsimd', 'for-next/insn', 'for-next/kbuild', 'for-next/kdump', 'for-next/mm', 'for-next/perf', 'for-next/selftests', 'for-next/stacks', 'for-next/trivial', 'for-next/uaccess' and 'for-next/undef-traps' into for-next/core")
This is a cross build, host ppc64le, target x86_64 allmodconfig.
drivers/perf/amlogic/meson_g12_ddr_pmu.c needs to include linux/io.h
(and your test builds probably got it (or asm/io.h) via some other
include file).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-11-22 4:52 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
2022-11-22 4:52 ` Stephen Rothwell [this message]
-- 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=20221122155216.47e0aca9@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=catalin.marinas@arm.com \
--cc=healych@amazon.com \
--cc=jiucheng.xu@amlogic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.