From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: jianqi.ren.cn@windriver.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y] cpufreq: amd-pstate: add check for cpufreq_cpu_get's return value
Date: Wed, 11 Dec 2024 11:32:56 -0500 [thread overview]
Message-ID: <20241211094948-3e6635f50a74424f@stable.kernel.org> (raw)
In-Reply-To: <20241211095352.2069266-1-jianqi.ren.cn@windriver.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 5493f9714e4cdaf0ee7cec15899a231400cb1a9f
WARNING: Author mismatch between patch and upstream commit:
Backport author: <jianqi.ren.cn@windriver.com>
Commit author: Anastasia Belova <abelova@astralinux.ru>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Not found
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
1: 5493f9714e4cd < -: ------------- cpufreq: amd-pstate: add check for cpufreq_cpu_get's return value
-: ------------- > 1: b42c647770dad cpufreq: amd-pstate: add check for cpufreq_cpu_get's return value
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
next prev parent reply other threads:[~2024-12-11 16:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 9:53 [PATCH 6.1.y] cpufreq: amd-pstate: add check for cpufreq_cpu_get's return value jianqi.ren.cn
2024-12-11 16:32 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-11 10:15 jianqi.ren.cn
2024-12-11 16:32 ` Sasha Levin
2024-12-09 4:19 jianqi.ren.cn
2024-12-09 10:07 ` Anastasia Belova
2024-12-09 14:35 ` Sasha Levin
2024-12-06 10:41 jianqi.ren.cn
2024-12-06 10:05 ` Greg KH
2024-12-06 17:11 ` Sasha Levin
2024-12-11 8:14 ` 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=20241211094948-3e6635f50a74424f@stable.kernel.org \
--to=sashal@kernel.org \
--cc=jianqi.ren.cn@windriver.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