From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [GIT PULL] arm64 fixes for -rc5
Date: Fri, 21 Jul 2023 12:44:23 +0100 [thread overview]
Message-ID: <20230721114423.GA12852@willie-the-truck> (raw)
Hi Linus,
I've picked up a handful of arm64 fixes while Catalin's been away, so here
they are. The tag has the usual summary, but we have basically have two
cleanups, a fix for an SME crash and a fix for hibernation.
There's a pending issue with memory hot-unplug in some configurations,
but we're still diagnosing that one.
Please pull.
Cheers,
Will
--->8
The following changes since commit 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5:
Linux 6.5-rc1 (2023-07-09 13:53:13 -0700)
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 d4d5be94a87872421ea2569044092535aff0b886:
arm64/fpsimd: Ensure SME storage is allocated after SVE VL changes (2023-07-21 11:11:09 +0100)
----------------------------------------------------------------
arm64 fixes for -rc3
- Fix saving of SME state after SVE vector length is changed
- Fix sparse warnings for missing vDSO function prototypes
- Fix hibernation resume path when kfence is enabled
- Fix field names for the HFGxTR_EL2 register
----------------------------------------------------------------
Marc Zyngier (1):
arm64: Fix HFGxTR_EL2 field naming
Mark Brown (1):
arm64/fpsimd: Ensure SME storage is allocated after SVE VL changes
Nikhil V (1):
arm64: mm: Make hibernation aware of KFENCE
Zhen Lei (1):
arm64: vdso: Clear common make C=2 warnings
arch/arm64/kernel/fpsimd.c | 33 +++++++++++++++++++++++++--------
arch/arm64/kernel/vdso/vgettimeofday.c | 4 ++++
arch/arm64/mm/trans_pgd.c | 4 +++-
arch/arm64/tools/sysreg | 12 ++++++------
4 files changed, 38 insertions(+), 15 deletions(-)
next reply other threads:[~2023-07-21 11:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 11:44 Will Deacon [this message]
2023-07-21 11:45 ` [GIT PULL] arm64 fixes for -rc5 Will Deacon
2023-07-21 17:28 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-02-16 11:58 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
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
2021-03-25 14:54 [GIT PULL] arm64: Fixes " Will Deacon
2021-03-25 19:13 ` pr-tracker-bot
2020-07-10 14:39 [GIT PULL] arm64 fixes " 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=20230721114423.GA12852@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).