From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
gregkh@linuxfoundation.org, rafael.j.wysocki@intel.com,
sumitg@nvidia.com, Christian Loehle <christian.loehle@arm.com>
Subject: Re: [PATCH 7.3 2/3] cpufreq: CPPC: Select the frequency-invariance callback per CPU
Date: Sun, 8 Nov 2026 19:34:35 -0500 [thread overview]
Message-ID: <2026-11-08-1-daily-reply-0007-cppc-7-3-p2@kernel.org> (raw)
In-Reply-To: <20261108112738.2566137-3-christian.loehle@arm.com>
> commit 21e018235d99bc86249b034c06646df8757b2852 upstream.
> cppc_cpufreq_cpu_fie_init() initializes deferred work only for CPUs whose
> feedback counters use PCC.
Patches 1 and 3 are queued for 7.3.
This one doesn't apply to the current 7.3 queue: 995e7d468070 ("cpufreq: CPPC:
Create the FIE worker before enabling PCC callbacks") adds
cppc_fie_kworker_init() in the PCC branch of cppc_cpufreq_cpu_fie_init().
Please rebase it on the queue and resend.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-11-09 0:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 11:27 [PATCH 7.3 0/3] CPPC stable backports Christian Loehle
2026-11-08 11:27 ` [PATCH 7.3 1/3] ACPI: CPPC: Validate FFH register fields before hardware access Christian Loehle
2026-11-08 11:27 ` [PATCH 7.3 2/3] cpufreq: CPPC: Select the frequency-invariance callback per CPU Christian Loehle
2026-11-09 0:34 ` Sasha Levin [this message]
2026-11-09 8:32 ` [PATCH 7.3] cpufreq: CPPC: Select the frequency-invariance callback, " Christian Loehle
2026-11-09 15:52 ` Sasha Levin
2026-11-08 11:27 ` [PATCH 7.3 3/3] ACPI: CPPC: Accept requests to retain immutable autonomous selection Christian Loehle
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=2026-11-08-1-daily-reply-0007-cppc-7-3-p2@kernel.org \
--to=sashal@kernel.org \
--cc=christian.loehle@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=rafael.j.wysocki@intel.com \
--cc=stable@vger.kernel.org \
--cc=sumitg@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.