From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64 fixes for -rc1
Date: Wed, 1 Mar 2017 04:51:56 +0000 [thread overview]
Message-ID: <20170301045156.GD12637@arm.com> (raw)
Hi Linus,
Please pull these three arm64 fixes for -rc1. The main fix here addresses a
kernel panic triggered on Qualcomm QDF2400 due to incorrect register usage
in an erratum workaround introduced during the merge window.
Cheers,
Will
--->8
The following changes since commit ffe7afd1713558d73483834c2e2d03a1e39a4062:
arm64/kprobes: consistently handle MRS/MSR with XZR (2017-02-15 12:20:29 +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 638f863dbbc8da16834ee0acc6ac10754f79c486:
arm64/cpufeature: check correct field width when updating sys_val (2017-02-24 11:14:12 +0000)
----------------------------------------------------------------
- Fix kernel panic on specific Qualcomm platform due to broken erratum
workaround
- Revert contiguous bit support due to TLB conflict aborts in simulation
- Don't treat all CPU ID register fields as 4-bit quantities
----------------------------------------------------------------
Mark Rutland (2):
Revert "arm64: mm: set the contiguous bit for kernel mappings where appropriate"
arm64/cpufeature: check correct field width when updating sys_val
Shanker Donthineni (1):
arm64: Avoid clobbering mm in erratum workaround on QDF2400
arch/arm64/include/asm/cpufeature.h | 14 ++++++++++----
arch/arm64/mm/mmu.c | 34 ++++------------------------------
arch/arm64/mm/proc.S | 2 +-
3 files changed, 15 insertions(+), 35 deletions(-)
next reply other threads:[~2017-03-01 4:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 4:51 Will Deacon [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-07 8:28 [GIT PULL] arm64 fixes for -rc1 Will Deacon
2025-10-07 16:13 ` pr-tracker-bot
2025-06-05 13:41 Will Deacon
2025-06-05 18:53 ` pr-tracker-bot
2024-07-26 8:42 Will Deacon
2024-07-26 18:07 ` pr-tracker-bot
2024-05-23 10:20 Will Deacon
2024-05-23 19:28 ` pr-tracker-bot
2024-01-19 16:05 Will Deacon
2024-01-19 16:34 ` Rob Herring
2024-01-19 16:58 ` Rob Herring
2024-01-19 22:50 ` pr-tracker-bot
2023-09-08 15:30 Will Deacon
2023-09-08 20:00 ` pr-tracker-bot
2023-05-04 14:22 Will Deacon
2023-05-04 19:49 ` pr-tracker-bot
2022-12-16 15:51 Will Deacon
2022-12-16 19:50 ` pr-tracker-bot
2021-11-10 18:52 Will Deacon
2021-11-10 20:09 ` pr-tracker-bot
2021-02-26 11:09 [GIT PULL] arm64: Fixes " Will Deacon
2021-02-26 18:31 ` pr-tracker-bot
2019-09-20 13:37 Will Deacon
2019-09-20 19:10 ` pr-tracker-bot
2019-01-04 18:24 [GIT PULL] arm64: fixes " Will Deacon
2019-01-05 20:20 ` pr-tracker-bot
2016-08-05 15:48 Will Deacon
2014-12-16 17:50 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=20170301045156.GD12637@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).