From: Zenghui Yu <yuzenghui@huawei.com>
To: <stable@vger.kernel.org>, <gregkh@linuxfoundation.org>,
<sashal@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<kvmarm@lists.cs.columbia.edu>, <linux-efi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <james.morse@arm.com>,
<anshuman.khandual@arm.com>, <catalin.marinas@arm.com>,
<will@kernel.org>, <maz@kernel.org>, <suzuki.poulose@arm.com>,
<ardb@kernel.org>, <mark.rutland@arm.com>,
<wanghaibin.wang@huawei.com>, <yuzenghui@huawei.com>,
<anders.roxell@linaro.org>
Subject: [PATCH 5.10 0/2] arm64: backport two patches to 5.10-stable
Date: Mon, 31 Oct 2022 19:22:44 +0800 [thread overview]
Message-ID: <20221031112246.1588-1-yuzenghui@huawei.com> (raw)
Patch #1 (merged in 5.12-rc3) is required to address the issue
Anders Roxell reported on the list [1]. Patch #2 (in 5.15-rc1) is
a follow up.
[1] https://lore.kernel.org/lkml/20220826120020.GB520@mutt
Anshuman Khandual (1):
arm64/kexec: Test page size support with new TGRAN range values
James Morse (1):
arm64/mm: Fix __enable_mmu() for new TGRAN range values
arch/arm64/include/asm/cpufeature.h | 9 ++++--
arch/arm64/include/asm/sysreg.h | 36 +++++++++++++++--------
arch/arm64/kernel/head.S | 6 ++--
arch/arm64/kvm/reset.c | 10 ++++---
drivers/firmware/efi/libstub/arm64-stub.c | 2 +-
5 files changed, 41 insertions(+), 22 deletions(-)
--
2.33.0
next reply other threads:[~2022-10-31 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 11:22 Zenghui Yu [this message]
2022-10-31 11:22 ` [PATCH 5.10 1/2] arm64/mm: Fix __enable_mmu() for new TGRAN range values Zenghui Yu
2022-10-31 11:22 ` [PATCH 5.10 2/2] arm64/kexec: Test page size support with " Zenghui Yu
2022-11-02 1:27 ` [PATCH 5.10 0/2] arm64: backport two patches to 5.10-stable Greg KH
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=20221031112246.1588-1-yuzenghui@huawei.com \
--to=yuzenghui@huawei.com \
--cc=anders.roxell@linaro.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=wanghaibin.wang@huawei.com \
--cc=will@kernel.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
all inboxes | Powered by JetHome®