From: Greg KH <gregkh@linuxfoundation.org>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: rafael@kernel.org, lenb@kernel.org, skelley@nvidia.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ACPI: CPPC: Fix related_cpus inconsistency during CPU hotplug
Date: Wed, 6 May 2026 07:23:01 +0200 [thread overview]
Message-ID: <2026050654-plus-reactive-d67a@gregkh> (raw)
In-Reply-To: <16c9b1e4-0ae4-4a81-90be-15b03f2ea176@huawei.com>
On Wed, May 06, 2026 at 11:30:03AM +0800, Jinjie Ruan wrote:
> +Cc Greg Kroah-Hartman
>
> Would it be appropriate to cherry-pick this change into the stable branch?
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
prev parent reply other threads:[~2026-05-06 5:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260417040112.3727756-1-ruanjinjie@huawei.com>
2026-05-06 3:30 ` [PATCH v2] ACPI: CPPC: Fix related_cpus inconsistency during CPU hotplug Jinjie Ruan
2026-05-06 5:23 ` Greg KH [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=2026050654-plus-reactive-d67a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=skelley@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox