From: Thomas Gleixner <tglx@linutronix.de>
To: Tiezhu Yang <yangtiezhu@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Marc Zyngier <maz@kernel.org>
Cc: loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
loongson-kernel@lists.loongnix.cn
Subject: Re: [PATCH] LoongArch: Give chance to build under !CONFIG_SMP
Date: Tue, 26 Mar 2024 11:02:00 +0100 [thread overview]
Message-ID: <87v859e2g7.ffs@tglx> (raw)
In-Reply-To: <20240326062101.9822-1-yangtiezhu@loongson.cn>
On Tue, Mar 26 2024 at 14:21, Tiezhu Yang wrote:
>
> This patch is based on 6.9-rc1. Please let me know if it is better to
> split it into two patches, the first one is for arch/loongarch and the
> second one is for drivers/irqchip.
Why are you asking? It's documented that patches should be split, no?
next prev parent reply other threads:[~2024-03-26 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 6:21 [PATCH] LoongArch: Give chance to build under !CONFIG_SMP Tiezhu Yang
2024-03-26 10:02 ` Thomas Gleixner [this message]
2024-03-26 11:26 ` Tiezhu Yang
2024-03-26 12:58 ` maobibo
2024-03-26 21:30 ` Tiezhu Yang
2024-03-27 1:09 ` maobibo
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=87v859e2g7.ffs@tglx \
--to=tglx@linutronix.de \
--cc=arnd@arndb.de \
--cc=chenhuacai@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=maz@kernel.org \
--cc=yangtiezhu@loongson.cn \
/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