From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Guo Ren <guoren@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>, <linux-sh@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<linux-csky@vger.kernel.org>
Subject: Re: [PATCH 0/3] Cleanup MAY_HAVE_SPARSE_IRQ
Date: Tue, 28 Sep 2021 13:43:16 +0800 [thread overview]
Message-ID: <3cd69b8f-c1af-baaa-31aa-f2e61e4c84b6@huawei.com> (raw)
In-Reply-To: <CAJF2gTRoXWqcMTkuu=L6gkF2cL79GonN6XBj86BMMptJnmz3zw@mail.gmail.com>
On 2021/9/28 13:08, Guo Ren wrote:
> On Mon, Sep 27, 2021 at 4:11 PM Kefeng Wang <wangkefeng.wang@huawei.com> wrote:
>> Most ARCHs support SPARSE_IRQ, and MAY_HAVE_SPARSE_IRQ is useless, and
>> only sh and csky select it, but the could use SPARSE_IRQ too, let's
>> kill MAY_HAVE_SPARSE_IRQ, also cleanup the kernel/irq/Kconfig a little.
> Can you elaborate the reason on why we need to kill MAY_HAVE_SPARSE_IRQ?
> What are the benefits after the patch? (As you know we couldn't drop
> "!SPARSE_IRQ".)
If csky want to keep MAY_HAVE_SPARSE_IRQ, then I won't kill it, or no
one use it,
then cleanup it.
prev parent reply other threads:[~2021-09-28 5:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 8:13 [PATCH 0/3] Cleanup MAY_HAVE_SPARSE_IRQ Kefeng Wang
2021-09-27 8:14 ` [PATCH 1/3] sh: Cleanup about SPARSE_IRQ Kefeng Wang
2021-09-27 14:29 ` Geert Uytterhoeven
2021-09-27 8:14 ` [PATCH 2/3] csky: Use SPARSE_IRQ Kefeng Wang
2021-09-28 3:39 ` Guo Ren
2021-09-28 4:47 ` Kefeng Wang
2021-09-27 8:14 ` [PATCH 3/3] genirq: Cleanup Kconfig Kefeng Wang
2021-09-27 12:09 ` [PATCH 0/3] Cleanup MAY_HAVE_SPARSE_IRQ Guo Ren
2021-09-27 12:35 ` Kefeng Wang
2021-09-27 14:08 ` Guo Ren
2021-09-28 5:08 ` Guo Ren
2021-09-28 5:43 ` Kefeng Wang [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=3cd69b8f-c1af-baaa-31aa-f2e61e4c84b6@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=dalias@libc.org \
--cc=guoren@kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=ysato@users.sourceforge.jp \
/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;
as well as URLs for NNTP newsgroup(s).