From: Marc Zyngier <maz@kernel.org>
To: Huacai Chen <chenhuacai@loongson.cn>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Xuefeng Li <lixuefeng@loongson.cn>,
Huacai Chen <chenhuacai@gmail.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH 1/2] irqchip: Adjust Kconfig for Loongson
Date: Tue, 31 May 2022 13:52:48 +0100 [thread overview]
Message-ID: <e7cf33a170d0b4e98e53744f60dbf922@kernel.org> (raw)
In-Reply-To: <20220531115942.1686812-1-chenhuacai@loongson.cn>
On 2022-05-31 12:59, Huacai Chen wrote:
> We are preparing to add new Loongson (based on LoongArch, not
> compatible
> with old MIPS-based Loongson) support.
Please drop this blurb from all your patches. It adds zero information.
> HTVEC will be shared by both old
> and new Loongson processors, so we adjust its description. HTPIC is
> only
> used by MIPS-based Loongson, so we add a MIPS dependency. PCH_PIC and
> PCH_MSI will have some arch-specific code, so we remove the
> COMPILE_TEST
> dependency to avoid build warnings.
>
> Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
No cover letter, no indication of what this applies on, no mention
of how this relates to the ongoing irqchip review.
What do you want me to do with this?
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2022-05-31 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 11:59 [PATCH 1/2] irqchip: Adjust Kconfig for Loongson Huacai Chen
2022-05-31 11:59 ` [PATCH 2/2] irqchip/loongson-liointc: Fix build error for LoongArch Huacai Chen
2022-05-31 12:52 ` Marc Zyngier [this message]
2022-05-31 15:53 ` [PATCH 1/2] irqchip: Adjust Kconfig for Loongson Huacai Chen
2022-06-02 11:35 ` Marc Zyngier
2022-06-02 13:14 ` Huacai Chen
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=e7cf33a170d0b4e98e53744f60dbf922@kernel.org \
--to=maz@kernel.org \
--cc=chenhuacai@gmail.com \
--cc=chenhuacai@loongson.cn \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--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.