public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Huacai Chen <chenhuacai@kernel.org>,
	WANG Xuerui <kernel@xen0n.name>
Cc: linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
	Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH v3 0/3] LoongArch: CPU parallel bring up
Date: Fri, 02 Aug 2024 16:17:47 +0200	[thread overview]
Message-ID: <871q37101g.ffs@tglx> (raw)
In-Reply-To: <20240716-loongarch-hotplug-v3-0-af59b3bb35c8@flygoat.com>

On Tue, Jul 16 2024 at 22:14, Jiaxun Yang wrote:
> This series implemented CPU parallel bring up for LoongArch.
>
> Being the first non-x86 arch enabling that we need to fix some
> infra in patch 1 and 2, then implement everything in patch 3.

I've merged the first two patches into

     git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp/core

and tagged them so the loongson tree can consume them to apply the
actual loongson change:

     git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp-for-loongson

Thanks,

        tglx


      parent reply	other threads:[~2024-08-02 14:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-16 14:14 [PATCH v3 0/3] LoongArch: CPU parallel bring up Jiaxun Yang
2024-07-16 14:14 ` [PATCH v3 1/3] cpu/hotplug: Make HOTPLUG_PARALLEL independent of HOTPLUG_SMT Jiaxun Yang
2024-08-02 14:25   ` [tip: smp/core] " tip-bot2 for Jiaxun Yang
2024-07-16 14:14 ` [PATCH v3 2/3] cpu/hotplug: Weak fallback for arch_cpuhp_init_parallel_bringup Jiaxun Yang
2024-08-02 14:25   ` [tip: smp/core] cpu/hotplug: Provide weak fallback for arch_cpuhp_init_parallel_bringup() tip-bot2 for Jiaxun Yang
2024-07-16 14:15 ` [PATCH v3 3/3] LoongArch: SMP: Implement parallel CPU bring up Jiaxun Yang
2024-08-02 14:17 ` Thomas Gleixner [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=871q37101g.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=chenhuacai@kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=kernel@xen0n.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=peterz@infradead.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