From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 fix for 5.9-rc1
Date: Sat, 8 Aug 2020 21:53:12 +0100 [thread overview]
Message-ID: <20200808205312.565-1-catalin.marinas@arm.com> (raw)
Hi Linus,
Please pull the arm64 updates below. The fix addresses a symbol export
for the tegra194-cpufreq module that made its way into mainline (the
issue was found in -next but still debating an alternative fix without
exporting __cpu_logical_map).
Thanks.
The following changes since commit 0e4cd9f2654915be8d09a1bd1b405ce5426e64c4:
Merge branch 'for-next/read-barrier-depends' into for-next/core (2020-07-31 18:09:57 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes
for you to fetch changes up to eaecca9e7710281be7c31d892c9f447eafd7ddd9:
arm64: Fix __cpu_logical_map undefined issue (2020-08-08 19:25:04 +0100)
----------------------------------------------------------------
- Fix tegra194-cpufreq module build failure caused __cpu_logical_map
not exported.
- Improve fixed_addresses comment regarding the fixmap buffer sizes.
----------------------------------------------------------------
Kefeng Wang (1):
arm64: Fix __cpu_logical_map undefined issue
Pingfan Liu (1):
arm64/fixmap: make notes of fixed_addresses more precisely
arch/arm64/include/asm/fixmap.h | 7 +++----
arch/arm64/include/asm/smp.h | 7 ++++++-
arch/arm64/kernel/setup.c | 8 +++++++-
arch/arm64/kernel/smp.c | 6 +++---
4 files changed, 19 insertions(+), 9 deletions(-)
next reply other threads:[~2020-08-08 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 20:53 Catalin Marinas [this message]
2020-08-08 21:19 ` [GIT PULL] arm64 fix for 5.9-rc1 pr-tracker-bot
2020-08-11 17:40 Catalin Marinas
2020-08-11 22:00 ` pr-tracker-bot
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=20200808205312.565-1-catalin.marinas@arm.com \
--to=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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).