From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Raghavendra Rao Ananta <rananta@google.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH] KVM: arm64: Ignore PMCNTENSET_EL0 while checking for overflow status
Date: Tue, 3 Dec 2024 18:34:13 -0500 [thread overview]
Message-ID: <20241203180911-dd0663d61317b9d3@stable.kernel.org> (raw)
In-Reply-To: <20241203190236.2711302-1-rananta@google.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 54bbee190d42166209185d89070c58a343bf514b
Status in newer kernel trees:
6.12.y | Present (different SHA1: 2a68705a5469)
Note: The patch differs from the upstream commit:
---
Failed to apply patch cleanly, falling back to interdiff...
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y | Failed | N/A |
| stable/linux-6.11.y | Failed | N/A |
| stable/linux-6.6.y | Failed | N/A |
| stable/linux-6.1.y | Failed | N/A |
| stable/linux-5.15.y | Failed | N/A |
| stable/linux-5.10.y | Failed | N/A |
| stable/linux-5.4.y | Success | Success |
| stable/linux-4.19.y | Success | Success |
next prev parent reply other threads:[~2024-12-04 0:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 15:05 FAILED: patch "[PATCH] KVM: arm64: Ignore PMCNTENSET_EL0 while checking for overflow" failed to apply to 4.19-stable tree gregkh
2024-12-03 19:02 ` [PATCH] KVM: arm64: Ignore PMCNTENSET_EL0 while checking for overflow status Raghavendra Rao Ananta
2024-12-03 23:34 ` Sasha Levin [this message]
2024-12-12 7:57 ` Greg KH
2024-12-12 8:27 ` Greg KH
2024-12-12 17:41 ` Raghavendra Rao Ananta
2024-12-12 18:07 ` Greg KH
2024-12-12 18:52 ` Raghavendra Rao Ananta
2024-12-13 7:22 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2024-12-16 17:54 Raghavendra Rao Ananta
2024-12-17 0:42 ` Sasha Levin
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=20241203180911-dd0663d61317b9d3@stable.kernel.org \
--to=sashal@kernel.org \
--cc=rananta@google.com \
--cc=stable@vger.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