From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: "Sasha Levin" <sashal@kernel.org>,
"Guixiong Wei" <weiguixiong@bytedance.com>,
"Srinivas Pandruvada" <srinivas.pandruvada@linux.intel.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: [PATCH 7.1.y] platform/x86/intel-uncore-freq: Fix current_freq_khz after CPU hotplug
Date: Tue, 21 Jul 2026 20:53:51 -0400 [thread overview]
Message-ID: <20260721201114.0004-stable-reply@kernel.org> (raw)
In-Reply-To: <20260721141743.28158-2-weiguixiong@bytedance.com>
> commit 6b63520ed14b17bbe9c2103debbd2152dde1fba3 upstream.
>
> When the last CPU of a legacy uncore die goes offline,
> uncore_freq_remove_die_entry() clears control_cpu. During CPU hotplug
> re-add, uncore_freq_add_entry() still populates sysfs attributes before
> assigning the new control CPU.
Queued for 7.1, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-22 0:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 15:03 FAILED: patch "[PATCH] platform/x86/intel-uncore-freq: Fix current_freq_khz after" failed to apply to 7.1-stable tree gregkh
2026-07-21 14:17 ` [PATCH 7.1.y] platform/x86/intel-uncore-freq: Fix current_freq_khz after CPU hotplug Guixiong Wei
2026-07-22 0:53 ` Sasha Levin [this message]
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=20260721201114.0004-stable-reply@kernel.org \
--to=sashal@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=weiguixiong@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox