From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>
Cc: Gavin Shan <gshan@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [PATCH] fix arm64 build with lack of __cpu_logical_map exported
Date: Sat, 8 Aug 2020 14:42:42 +0200 [thread overview]
Message-ID: <20200808124242.GA352821@kroah.com> (raw)
Currently Linus's tree fails with the following build error on arm64
makeallmodconfig:
ERROR: modpost: "__cpu_logical_map" [drivers/cpufreq/tegra194-cpufreq.ko] undefined!
Seems that kernel.ci also notices this for the past 2 days:
https://lore.kernel.org/r/5f2c97ab.1c69fb81.160f4.0196@mx.google.com
https://lore.kernel.org/r/5f2ab734.1c69fb81.24b16.8537@mx.google.com
Fix this up by just exporting the symbol. Don't know if it's the
"right" fix, but it solves the build error for my machines.
Reported-by: "kernelci.org bot" <bot@kernelci.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
diff --git a/arch/arm64/kernel/setup.c b/arch/arm64/kernel/setup.c
index 87e81d29e6fb..b421a4756793 100644
--- a/arch/arm64/kernel/setup.c
+++ b/arch/arm64/kernel/setup.c
@@ -275,6 +275,7 @@ static int __init reserve_memblock_reserved_regions(void)
arch_initcall(reserve_memblock_reserved_regions);
u64 __cpu_logical_map[NR_CPUS] = { [0 ... NR_CPUS-1] = INVALID_HWID };
+EXPORT_SYMBOL_GPL(__cpu_logical_map);
void __init __no_sanitize_address setup_arch(char **cmdline_p)
{
next reply other threads:[~2020-08-08 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 12:42 Greg Kroah-Hartman [this message]
2020-08-08 15:05 ` [PATCH] fix arm64 build with lack of __cpu_logical_map exported Catalin Marinas
2020-08-08 15:29 ` Greg Kroah-Hartman
2020-08-08 18:29 ` Catalin Marinas
2020-08-09 7:14 ` Greg Kroah-Hartman
2020-08-10 7:45 ` Sudeep Holla
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=20200808124242.GA352821@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=catalin.marinas@arm.com \
--cc=gshan@redhat.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=sudeep.holla@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).