linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Thomas Gleixner <tglx@linutronix.de>, Guo Ren <guoren@kernel.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Rich Felker <dalias@libc.org>, <linux-sh@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-csky@vger.kernel.org>
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: [PATCH 0/3] Cleanup MAY_HAVE_SPARSE_IRQ
Date: Mon, 27 Sep 2021 16:13:59 +0800	[thread overview]
Message-ID: <20210927081402.191717-1-wangkefeng.wang@huawei.com> (raw)

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.

Kefeng Wang (3):
  sh: Cleanup about SPARSE_IRQ
  csky: Use SPARSE_IRQ
  genirq: Cleanup Kconfig

 arch/csky/Kconfig         |  2 +-
 arch/sh/Kconfig           |  1 -
 arch/sh/include/asm/irq.h |  9 -------
 kernel/irq/Kconfig        | 50 ++++++++++++++++-----------------------
 4 files changed, 21 insertions(+), 41 deletions(-)

-- 
2.26.2


             reply	other threads:[~2021-09-27  8:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27  8:13 Kefeng Wang [this message]
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

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=20210927081402.191717-1-wangkefeng.wang@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 \
    --subject='Re: [PATCH 0/3] Cleanup MAY_HAVE_SPARSE_IRQ' \
    /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

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).