From: Greg KH <gregkh@linuxfoundation.org>
To: Zenghui Yu <yuzenghui@huawei.com>
Cc: stable@vger.kernel.org, sashal@kernel.org,
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, anders.roxell@linaro.org
Subject: Re: [PATCH 5.10 0/2] arm64: backport two patches to 5.10-stable
Date: Wed, 2 Nov 2022 02:27:52 +0100 [thread overview]
Message-ID: <Y2HHmEUEHShi4PMX@kroah.com> (raw)
In-Reply-To: <20221031112246.1588-1-yuzenghui@huawei.com>
On Mon, Oct 31, 2022 at 07:22:44PM +0800, Zenghui Yu wrote:
> 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
Both now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-11-02 1:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 11:22 [PATCH 5.10 0/2] arm64: backport two patches to 5.10-stable Zenghui Yu
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 ` Greg KH [this message]
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=Y2HHmEUEHShi4PMX@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anders.roxell@linaro.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--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 \
--cc=yuzenghui@huawei.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