From: Zenghui Yu <yuzenghui@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <stable@vger.kernel.org>, <sashal@kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <kvmarm@lists.linux.dev>,
<andrew.murray@arm.com>, <mark.rutland@arm.com>,
<suzuki.poulose@arm.com>, <wanghaibin.wang@huawei.com>,
<will@kernel.org>
Subject: Re: [for-4.19 0/2] backport "KVM: arm64: limit PMU version to PMUv3 for ARMv8.1"
Date: Tue, 28 Nov 2023 20:00:08 +0800 [thread overview]
Message-ID: <350d1f6f-953b-eac4-4e1b-9e59060c99bc@huawei.com> (raw)
In-Reply-To: <2023112831-preachy-unshaved-790d@gregkh>
On 2023/11/28 16:12, Greg KH wrote:
> On Tue, Nov 28, 2023 at 03:46:31PM +0800, Zenghui Yu wrote:
>> We need to backport patch #1 as well because it introduced a helper used
>> by patch #2.
>>
>> Andrew Murray (2):
>> arm64: cpufeature: Extract capped perfmon fields
>> KVM: arm64: limit PMU version to PMUv3 for ARMv8.1
>
> We can not just take these in an old stable tree and not newer ones as
> that would mean you could upgrade and have a regression. Please provide
> backports for all applicable stable trees and we will be glad to take
> them.
Thanks for the heads up! "for-5.4" patches sent now.
Zenghui
next prev parent reply other threads:[~2023-11-28 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 7:46 [for-4.19 0/2] backport "KVM: arm64: limit PMU version to PMUv3 for ARMv8.1" Zenghui Yu
2023-11-28 7:46 ` [for-4.19 1/2] arm64: cpufeature: Extract capped perfmon fields Zenghui Yu
2023-11-28 7:46 ` [for-4.19 2/2] KVM: arm64: limit PMU version to PMUv3 for ARMv8.1 Zenghui Yu
2023-11-28 8:12 ` [for-4.19 0/2] backport "KVM: arm64: limit PMU version to PMUv3 for ARMv8.1" Greg KH
2023-11-28 12:00 ` Zenghui Yu [this message]
2023-11-30 13:40 ` 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=350d1f6f-953b-eac4-4e1b-9e59060c99bc@huawei.com \
--to=yuzenghui@huawei.com \
--cc=andrew.murray@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--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