From: Catalin Marinas <catalin.marinas@arm.com>
To: Jessica Yu <jeyu@kernel.org>,
linux-kernel@vger.kernel.org, Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will@kernel.org>, Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH] arm64: Remove exporting cpu_logical_map symbol
Date: Wed, 2 Sep 2020 08:41:18 +0100 [thread overview]
Message-ID: <20200902074117.GA28265@gaia> (raw)
In-Reply-To: <159903220030.29783.7186911071188549924.b4-ty@arm.com>
On Wed, Sep 02, 2020 at 08:37:03AM +0100, Catalin Marinas wrote:
> On Tue, 1 Sep 2020 10:52:29 +0100, Sudeep Holla wrote:
> > Commit eaecca9e7710 ("arm64: Fix __cpu_logical_map undefined issue")
> > exported cpu_logical_map in order to fix tegra194-cpufreq module build
> > failure.
> >
> > As this might potentially cause problem while supporting physical CPU
> > hotplug, tegra194-cpufreq module was reworded to avoid use of
> > cpu_logical_map() via the commit 93d0c1ab2328 ("cpufreq: replace
> > cpu_logical_map() with read_cpuid_mpir()")
> >
> > [...]
>
> Applied to arm64 (for-next/fixes), thanks!
>
> [1/1] arm64: Remove exporting cpu_logical_map symbol
> https://git.kernel.org/arm64/c/60295d50958e
Either my script on top of b4 is broken or b4 0.5.2 has a bug. It was
supposed to only reply to Sudeep here but somehow combined it with the
recipient list from Jessica's patch (arm64/module: set trampoline
section flags regardless of CONFIG_DYNAMIC_FTRACE).
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-09-02 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 9:52 [PATCH] arm64: Remove exporting cpu_logical_map symbol Sudeep Holla
[not found] ` <159903220030.29783.7186911071188549924.b4-ty@arm.com>
2020-09-02 7:41 ` Catalin Marinas [this message]
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=20200902074117.GA28265@gaia \
--to=catalin.marinas@arm.com \
--cc=ardb@kernel.org \
--cc=jeyu@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=peterz@infradead.org \
--cc=sudeep.holla@arm.com \
--cc=szabolcs.nagy@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).