linux-kernel - [PATCH v2 0/3] Cleanup MAY_HAVE_SPARSE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20210929023522.57732-1-wangkefeng.wang@huawei.com>
Date:   Wed, 29 Sep 2021 10:35:19 +0800
From:   Kefeng Wang <wangkefeng.wang@...wei.com>
To:     Thomas Gleixner <tglx@...utronix.de>, Guo Ren <guoren@...nel.org>,
        Yoshinori Sato <ysato@...rs.sourceforge.jp>,
        Rich Felker <dalias@...c.org>, <linux-sh@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <linux-csky@...r.kernel.org>
CC:     Kefeng Wang <wangkefeng.wang@...wei.com>
Subject: [PATCH v2 0/3] Cleanup MAY_HAVE_SPARSE_IRQ

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

-- 
2.26.2