From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will.deacon@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 fixes for 4.14-rc4
Date: Fri, 6 Oct 2017 19:24:28 +0100 [thread overview]
Message-ID: <20171006182426.udiie6pplnklwv5a@armageddon.cambridge.arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below. Thanks.
The following changes since commit 9e66317d3c92ddaab330c125dfe9d06eee268aff:
Linux 4.14-rc3 (2017-10-01 14:54:54 -0700)
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 ae2e972dae3cea795e9f8f94eb1601213c2d49f0:
arm64: Ensure fpsimd support is ready before userspace is active (2017-10-06 16:35:25 +0100)
----------------------------------------------------------------
arm64 fixes:
- Bring initialisation of user space undefined instruction handling
early (core_initcall) since late_initcall() happens after modprobe in
initramfs is invoked. Similar fix for fpsimd initialisation
- Increase the kernel stack when KASAN is enabled
- Bring the PCI ACS enabling earlier via the
iort_init_platform_devices()
- Fix misleading data abort address printing (decimal vs hex)
----------------------------------------------------------------
Lorenzo Pieralisi (1):
ACPI/IORT: Fix PCI ACS enablement
Mark Rutland (2):
arm64: fix misleading data abort decoding
arm64: Use larger stacks when KASAN is selected
Suzuki K Poulose (2):
arm64: Ensure the instruction emulation is ready for userspace
arm64: Ensure fpsimd support is ready before userspace is active
arch/arm64/include/asm/memory.h | 9 ++++++---
arch/arm64/kernel/armv8_deprecated.c | 2 +-
arch/arm64/kernel/cpufeature.c | 2 +-
arch/arm64/kernel/fpsimd.c | 2 +-
arch/arm64/mm/fault.c | 2 +-
drivers/acpi/arm64/iort.c | 35 +++++++++++++++++++++++++++++++++++
6 files changed, 45 insertions(+), 7 deletions(-)
--
Catalin
reply other threads:[~2017-10-06 18:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20171006182426.udiie6pplnklwv5a@armageddon.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
/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).