From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, marmarek@invisiblethingslab.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.14.y and others] cpufreq: Reference count policy in cpufreq_update_limits()
Date: Sat, 19 Apr 2025 07:50:46 -0400 [thread overview]
Message-ID: <20250418200224-f13c7b3ffe6c36e2@stable.kernel.org> (raw)
In-Reply-To: <20250418021517.1960418-1-marmarek@invisiblethingslab.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Found matching upstream commit but patch is missing proper reference to it
Found matching upstream commit: 9e4e249018d208678888bdf22f6b652728106528
WARNING: Author mismatch between patch and found commit:
Backport author: <marmarek@invisiblethingslab.com>
Commit author: Rafael J. Wysocki<rafael.j.wysocki@intel.com>
Note: The patch differs from the upstream commit:
---
1: 9e4e249018d20 ! 1: cd95c6b965176 cpufreq: Reference count policy in cpufreq_update_limits()
@@ Commit message
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Link: https://patch.msgid.link/1928789.tdWV9SEqCh@rjwysocki.net
+ (cherry picked from commit 9e4e249018d208678888bdf22f6b652728106528)
+ [do not use __free(cpufreq_cpu_put) in a backport]
+ Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
## drivers/cpufreq/cpufreq.c ##
@@ drivers/cpufreq/cpufreq.c: EXPORT_SYMBOL(cpufreq_update_policy);
*/
void cpufreq_update_limits(unsigned int cpu)
{
-+ struct cpufreq_policy *policy __free(put_cpufreq_policy);
++ struct cpufreq_policy *policy;
+
+ policy = cpufreq_cpu_get(cpu);
+ if (!policy)
@@ drivers/cpufreq/cpufreq.c: EXPORT_SYMBOL(cpufreq_update_policy);
if (cpufreq_driver->update_limits)
cpufreq_driver->update_limits(cpu);
else
+ cpufreq_update_policy(cpu);
++
++ cpufreq_cpu_put(policy);
+ }
+ EXPORT_SYMBOL_GPL(cpufreq_update_limits);
+
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.14.y | Success | Success |
next prev parent reply other threads:[~2025-04-19 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 13:28 FAILED: patch "[PATCH] cpufreq: Reference count policy in cpufreq_update_limits()" failed to apply to 6.14-stable tree gregkh
2025-04-17 23:52 ` Marek Marczykowski-Górecki
2025-04-18 1:51 ` Marek Marczykowski-Górecki
2025-04-18 2:15 ` [PATCH 6.14.y and others] cpufreq: Reference count policy in cpufreq_update_limits() Marek Marczykowski-Górecki
2025-04-19 11:50 ` Sasha Levin [this message]
2025-04-19 15:31 ` Wysocki, Rafael J
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=20250418200224-f13c7b3ffe6c36e2@stable.kernel.org \
--to=sashal@kernel.org \
--cc=marmarek@invisiblethingslab.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