From: bibo mao <maobibo@loongson.cn>
To: Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Marc Zyngier <maz@kernel.org>
Cc: "Jianmin Lv" <lvjianmin@loongson.cn>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v5 0/2] irqchip/loongson-eiointc: Add simple irq routing method
Date: Wed, 26 Jul 2023 17:45:51 +0800 [thread overview]
Message-ID: <f19c393b-8c2e-e3aa-988a-88a423b59b99@loongson.cn> (raw)
In-Reply-To: <20230719063558.3131045-1-maobibo@loongson.cn>
slight ping :)
在 2023/7/19 14:35, Bibo Mao 写道:
> Fix return value checking of eiointc_index where int type
> is converted uint32_t and check smaller than 0.
>
> Add simple irq route support on system with only one eiointc node,
> rather than use anysend method.
>
> ---
> Changes in v5:
> Modify typo issue.
>
> Changes in v4:
> Modify some spell checking problems.
> Add Fixes tag.
>
> Changes in v3:
> Modify some spell checking problems.
>
> Changes in v2:
> Use the simple irq routing on embeded board like 2K0500 and 2K2000
> board, since there is only one eio node.
>
> ---
> Bibo Mao (2):
> irqchip/loongson-eiointc: Fix return value checking of eiointc_index
> irqchip/loongson-eiointc: Simplify irq routing on some platforms
>
> drivers/irqchip/irq-loongson-eiointc.c | 93 +++++++++++++++++++++++---
> 1 file changed, 82 insertions(+), 11 deletions(-)
>
next prev parent reply other threads:[~2023-07-26 9:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 6:35 Bibo Mao
2023-07-19 6:35 ` [PATCH v5 1/2] irqchip/loongson-eiointc: Fix return value checking of eiointc_index Bibo Mao
2023-07-19 6:35 ` [PATCH v5 2/2] irqchip/loongson-eiointc: Simplify irq routing on some platforms Bibo Mao
2023-07-26 9:45 ` bibo mao [this message]
2023-07-26 9:53 ` [PATCH v5 0/2] irqchip/loongson-eiointc: Add simple irq routing method Marc Zyngier
2023-07-26 10:08 ` bibo mao
2023-07-31 14:16 ` Huacai Chen
2023-08-01 1:42 ` bibo mao
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=f19c393b-8c2e-e3aa-988a-88a423b59b99@loongson.cn \
--to=maobibo@loongson.cn \
--cc=chenhuacai@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lvjianmin@loongson.cn \
--cc=maz@kernel.org \
--cc=philmd@linaro.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
all inboxes | Powered by JetHome®