From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Thomas Gleixner <tglx@linutronix.de>, Guo Ren <guoren@kernel.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
<linux-sh@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-csky@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] Cleanup MAY_HAVE_SPARSE_IRQ
Date: Tue, 19 Oct 2021 20:30:26 +0800 [thread overview]
Message-ID: <3c64a5a1-128a-7448-f429-b2d195819ca2@huawei.com> (raw)
In-Reply-To: <20210929023522.57732-1-wangkefeng.wang@huawei.com>
Hi Thomas, Could you pickup this cleanup patchset from your tree if
possible, thanks.
On 2021/9/29 10:35, Kefeng Wang wrote:
> Most ARCHs support SPARSE_IRQ, the dynamical and statical irq
> description allocation are alternative.
>
> The last user of MAY_HAVE_SPARSE_IRQ is sh/csky, but the sh use
> SPARSE_IRQ, MAY_HAVE_SPARSE_IRQ could be kill. and for csky, it
> uses statical allocation by default.
>
> So MAY_HAVE_SPARSE_IRQ seems to be useless, no need to maintain a
> separate MAY_HAVE_SPARSE_IRQ config, kill it.
>
> Also cleanup the kernel/irq/Kconfig a little.
>
> v2:
> - drop all the NR_IRQS suggested by Geert
> - don' use SPARSE_IRQ for csky by default, suggested by Guo.
>
> Kefeng Wang (3):
> sh: Cleanup about SPARSE_IRQ
> csky: Kill MAY_HAVE_SPARSE_IRQ
> genirq: Cleanup Kconfig
>
> arch/csky/Kconfig | 1 -
> arch/sh/Kconfig | 1 -
> arch/sh/include/asm/irq.h | 11 ---------
> kernel/irq/Kconfig | 50 ++++++++++++++++-----------------------
> 4 files changed, 20 insertions(+), 43 deletions(-)
>
prev parent reply other threads:[~2021-10-19 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 2:35 [PATCH v2 0/3] Cleanup MAY_HAVE_SPARSE_IRQ Kefeng Wang
2021-09-29 2:35 ` [PATCH v1 1/3] sh: Cleanup about SPARSE_IRQ Kefeng Wang
2021-09-29 2:35 ` [PATCH v2 2/3] csky: Kill MAY_HAVE_SPARSE_IRQ Kefeng Wang
2021-09-29 2:35 ` [PATCH v3 3/3] genirq: Cleanup Kconfig Kefeng Wang
2021-09-29 7:21 ` [PATCH v2 0/3] Cleanup MAY_HAVE_SPARSE_IRQ Geert Uytterhoeven
2021-09-29 8:12 ` Kefeng Wang
2021-10-19 12:30 ` 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=3c64a5a1-128a-7448-f429-b2d195819ca2@huawei.com \
--to=wangkefeng.wang@huawei.com \
--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).