From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>,
kernel-team@android.com
Subject: [GIT PULL] arm64: Fixes for -rc5
Date: Thu, 25 Mar 2021 14:54:43 +0000 [thread overview]
Message-ID: <20210325145443.GA15172@willie-the-truck> (raw)
Hi Linus,
Please pull these arm64 fixes for -rc5. Minor fixes all over, ranging
from typos to tests to errata workarounds. Summary in the tag.
Cheers,
Will
--->8
The following changes since commit c8e3866836528a4ba3b0535834f03768d74f7d8e:
perf/arm_dmc620_pmu: Fix error return code in dmc620_pmu_device_probe() (2021-03-12 11:30:31 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes
for you to fetch changes up to 20109a859a9b514eb10c22b8a14b5704ffe93897:
arm64: kernel: disable CNP on Carmel (2021-03-25 10:00:23 +0000)
----------------------------------------------------------------
arm64 fixes for -rc5
- Fix possible memory hotplug failure with KASLR
- Fix FFR value in SVE kselftest
- Fix backtraces reported in /proc/$pid/stack
- Disable broken CnP implementation on NVIDIA Carmel
- Typo fixes and ACPI documentation clarification
- Fix some W=1 warnings
----------------------------------------------------------------
Alex Elder (1):
arm64: csum: cast to the proper type
Andre Przywara (1):
kselftest/arm64: sve: Do not use non-canonical FFR register value
Bhaskar Chowdhury (1):
arm64: cpuinfo: Fix a typo
Maninder Singh (1):
arm64/process.c: fix Wmissing-prototypes build warnings
Mark Rutland (1):
arm64: stacktrace: don't trace arch_stack_walk()
Pavel Tatashin (2):
arm64: kdump: update ppos when reading elfcorehdr
arm64: mm: correct the inside linear map range during hotplug check
Rich Wiley (1):
arm64: kernel: disable CNP on Carmel
Tom Saeger (1):
Documentation: arm64/acpi : clarify arm64 support of IBFT
Documentation/arm64/acpi_object_usage.rst | 10 +++++-----
Documentation/arm64/silicon-errata.rst | 3 +++
arch/arm64/Kconfig | 10 ++++++++++
arch/arm64/include/asm/checksum.h | 2 +-
arch/arm64/include/asm/cpucaps.h | 3 ++-
arch/arm64/include/asm/processor.h | 2 ++
arch/arm64/include/asm/thread_info.h | 2 ++
arch/arm64/kernel/cpu_errata.c | 8 ++++++++
arch/arm64/kernel/cpufeature.c | 5 ++++-
arch/arm64/kernel/cpuinfo.c | 2 +-
arch/arm64/kernel/crash_dump.c | 2 ++
arch/arm64/kernel/process.c | 2 ++
arch/arm64/kernel/stacktrace.c | 9 +++++----
arch/arm64/mm/mmu.c | 21 +++++++++++++++++++--
tools/testing/selftests/arm64/fp/sve-test.S | 22 +++++++++++++++++-----
15 files changed, 83 insertions(+), 20 deletions(-)
next reply other threads:[~2021-03-25 14:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 14:54 Will Deacon [this message]
2021-03-25 19:13 ` [GIT PULL] arm64: Fixes for -rc5 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-02-16 11:58 [GIT PULL] arm64 fixes " Will Deacon
2024-02-16 18:52 ` pr-tracker-bot
2023-10-06 7:56 Will Deacon
2023-10-06 15:15 ` pr-tracker-bot
2023-07-21 11:44 Will Deacon
2023-07-21 11:45 ` Will Deacon
2023-07-21 17:28 ` pr-tracker-bot
2022-09-11 11:37 Will Deacon
2022-09-11 19:36 ` pr-tracker-bot
2021-08-06 13:53 Will Deacon
2021-08-06 18:40 ` Linus Torvalds
2021-08-09 10:52 ` Will Deacon
2021-08-06 18:48 ` pr-tracker-bot
2020-07-10 14:39 Will Deacon
2020-07-10 16:55 ` pr-tracker-bot
2020-03-06 15:12 Will Deacon
2020-03-06 20:55 ` pr-tracker-bot
2019-06-14 15:02 [GIT PULL] arm64: " Will Deacon
2019-06-14 16:20 ` pr-tracker-bot
2019-04-12 16:05 [GIT PULL] arm64 " Will Deacon
2019-04-13 17:40 ` pr-tracker-bot
2019-02-01 17:51 [GIT PULL] arm64: " Will Deacon
2019-02-02 1:00 ` pr-tracker-bot
2018-05-11 17:30 Will Deacon
2017-03-31 17:15 Will Deacon
2016-06-24 11:41 Will Deacon
2016-02-19 16:29 Will Deacon
2015-10-07 14:20 Will Deacon
2015-01-16 17:16 Will Deacon
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=20210325145443.GA15172@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).