From: Sasha Levin <sashal@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Huacai Chen <chenhuacai@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>, Xuerui Wang <kernel@xen0n.name>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
loongarch@lists.linux.dev, Huacai Chen <chenhuacai@loongson.cn>
Subject: Re: [PATCH 6.1 & 6.6] LoongArch: Report dying CPU to RCU in stop_this_cpu()
Date: Fri, 3 Jul 2026 22:05:08 -0400 [thread overview]
Message-ID: <2026070315-stable-reply-0014@kernel.org> (raw)
In-Reply-To: <20260703032401.857553-1-chenhuacai@loongson.cn>
On Thu, Jul 03, 2026 at 11:24:00AM +0800, Huacai Chen wrote:
> commit f2539c56c74691e7a88af6372ba2b48c06ed2fe4 upstream.
>
> This is a port of MIPS commit 9f3f3bdc6d9dac1 ("MIPS: smp: report dying
> CPU to RCU in stop_this_cpu()"). smp_send_stop() parks all secondary
> CPUs in stop_this_cpu().
Queued for 6.6.y and 6.1.y, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-04 2:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 3:24 [PATCH 6.1 & 6.6] LoongArch: Report dying CPU to RCU in stop_this_cpu() Huacai Chen
2026-07-04 2:05 ` 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=2026070315-stable-reply-0014@kernel.org \
--to=sashal@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--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