linux-kernel - Re: [PATCH 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJF2gTRoXWqcMTkuu=L6gkF2cL79GonN6XBj86BMMptJnmz3zw@mail.gmail.com>
Date:   Tue, 28 Sep 2021 13:08:56 +0800
From:   Guo Ren <guoren@...nel.org>
To:     Kefeng Wang <wangkefeng.wang@...wei.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Yoshinori Sato <ysato@...rs.sourceforge.jp>,
        Rich Felker <dalias@...c.org>, linux-sh@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-csky@...r.kernel.org
Subject: Re: [PATCH 0/3] Cleanup MAY_HAVE_SPARSE_IRQ

On Mon, Sep 27, 2021 at 4:11 PM Kefeng Wang <wangkefeng.wang@...wei.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".)

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


-- 
Best Regards
 Guo Ren

ML: https://lore.kernel.org/linux-csky/