From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
kernel-team@android.com
Subject: [GIT PULL] arm64 merge window fixes for -rc1
Date: Thu, 11 Jun 2020 18:34:12 +0100 [thread overview]
Message-ID: <20200611173412.GA9575@willie-the-truck> (raw)
Hi Linus,
Please pull these arm64 fixes that came in during the merge window. They'll
probably be more to come, but it doesn't seem like it's worth me sitting
on these in the meantime.
Summary in the tag.
Cheers,
Will
--->8
The following changes since commit 082af5ec5080b028f7d0846a6c27cbb87f288205:
Merge branch 'for-next/scs' into for-next/core (2020-05-28 18:03:40 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-upstream
for you to fetch changes up to dd4bc60765873445893037ae73a5f75398a8cd19:
arm64: warn on incorrect placement of the kernel by the bootloader (2020-06-11 14:13:13 +0100)
----------------------------------------------------------------
arm64 merge window fixes for -rc1
- Fix SCS debug check to report max stack usage in bytes as advertised
- Fix typo: CONFIG_FTRACE_WITH_REGS => CONFIG_DYNAMIC_FTRACE_WITH_REGS
- Fix incorrect mask in HiSilicon L3C perf PMU driver
- Fix compat vDSO compilation under some toolchain configurations
- Fix false UBSAN warning from ACPI IORT parsing code
- Fix booting under bootloaders that ignore TEXT_OFFSET
- Annotate debug initcall function with '__init'
----------------------------------------------------------------
Ard Biesheuvel (1):
arm64: warn on incorrect placement of the kernel by the bootloader
Christophe JAILLET (1):
arm64: debug: mark a function as __init to save some memory
Joe Perches (1):
arm64: ftrace: Change CONFIG_FTRACE_WITH_REGS to CONFIG_DYNAMIC_FTRACE_WITH_REGS
Nick Desaulniers (2):
arm64: vdso32: add CONFIG_THUMB2_COMPAT_VDSO
arm64: acpi: fix UBSAN warning
Shaokun Zhang (1):
drivers/perf: hisi: Fix wrong value for all counters enable
Will Deacon (1):
scs: Report SCS usage in bytes rather than number of entries
arch/arm64/Kconfig | 11 ++++++++++-
arch/arm64/include/asm/acpi.h | 5 +++--
arch/arm64/kernel/debug-monitors.c | 2 +-
arch/arm64/kernel/ftrace.c | 3 ++-
arch/arm64/kernel/setup.c | 4 ++++
arch/arm64/kernel/vdso32/Makefile | 8 ++++++++
drivers/perf/hisilicon/hisi_uncore_l3c_pmu.c | 2 +-
kernel/scs.c | 2 +-
8 files changed, 30 insertions(+), 7 deletions(-)
next reply other threads:[~2020-06-11 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 17:34 Will Deacon [this message]
2020-06-11 22:00 ` [GIT PULL] arm64 merge window fixes for -rc1 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2018-08-17 16:36 [GIT PULL] arm64: " 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=20200611173412.GA9575@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).