linux-kernel - Re: [PATCH] irqchip: define EXYNOS_IRQ

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] [day] [month] [year] [list]

Message-ID: <439a4d91787deaff44d2203e32b74ea3@www.loen.fr>
Date:   Thu, 05 Dec 2019 16:01:36 +0000
From:   Marc Zyngier <maz@...nel.org>
To:     Hyunki Koo <hyunki00.koo@...il.com>
Cc:     Krzysztof Kozlowski <krzk@...nel.org>, <tglx@...utronix.de>,
        Hyunki Koo <hyunki00.koo@...sung.com>,
        Jason Cooper <jason@...edaemon.net>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] irqchip: define EXYNOS_IRQ_COMBINER

On 2019-12-05 15:44, Hyunki Koo wrote:
> there is no new driver
>
> I just want remove direct dependency between ARCH_EXYNOS and
> exynos-combiner.c
>
> because all exynos device is not needed the exynos-combiner
>
> only used in aarch32 devices.

So breaking all existing configurations (that will rely on this
driver to be selected by ARCH_EXYNOS) is absolutely fine, as long
as your pet machine is not "polluted" by an unnecessary driver?

I'm sorry, but that's not acceptable.

         M.
-- 
Jazz is not dead. It just smells funny...