From: Frederic Weisbecker <frederic@kernel.org>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: Bibo Mao <maobibo@loongson.cn>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
Xianglai Li <lixianglai@loongson.cn>
Subject: Re: [PATCH v2 2/2] LoongArch: Remove clockevents shutdown call on offlining
Date: Thu, 4 Sep 2025 16:43:54 +0200 [thread overview]
Message-ID: <aLmlqn6snsiGRV14@localhost.localdomain> (raw)
In-Reply-To: <CAAhV-H6ThTR+r6m-moVpLTLVsV9ozfwaJPBuwZ+VdHDXsamwTQ@mail.gmail.com>
Le Thu, Sep 04, 2025 at 10:28:28PM +0800, Huacai Chen a écrit :
> On Thu, Sep 4, 2025 at 10:10 PM Frederic Weisbecker <frederic@kernel.org> wrote:
> >
> > Le Thu, Sep 04, 2025 at 03:17:32PM +0800, Bibo Mao a écrit :
> > > The clockevents core already detached and unregistered it at this stage.
> > >
> > > Signed-off-by: Bibo Mao <maobibo@loongson.cn>
> >
> > Reviewed-by: Frederic Weisbecker <frederic@kernel.org>
> If I'm right, I should pick this patch after the first one be merged?
Exactly!
Thanks.
> Huacai
>
> >
> > --
> > Frederic Weisbecker
> > SUSE Labs
> >
--
Frederic Weisbecker
SUSE Labs
prev parent reply other threads:[~2025-09-04 14:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 7:17 [PATCH v2 0/2] Remove unreasonable detached state set in tick_shutdown() Bibo Mao
2025-09-04 7:17 ` [PATCH v2 1/2] tick: " Bibo Mao
2025-09-04 10:33 ` Frederic Weisbecker
2025-09-04 15:57 ` Thomas Gleixner
2025-09-04 16:08 ` Frederic Weisbecker
2025-09-05 2:04 ` Bibo Mao
2025-09-05 7:41 ` Thomas Gleixner
2025-09-04 7:17 ` [PATCH v2 2/2] LoongArch: Remove clockevents shutdown call on offlining Bibo Mao
2025-09-04 14:10 ` Frederic Weisbecker
2025-09-04 14:28 ` Huacai Chen
2025-09-04 14:43 ` Frederic Weisbecker [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=aLmlqn6snsiGRV14@localhost.localdomain \
--to=frederic@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=chenhuacai@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixianglai@loongson.cn \
--cc=loongarch@lists.linux.dev \
--cc=maobibo@loongson.cn \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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.