linux-kernel - Re: [PATCH 3/3] bus: hisi_lpc: Expand build test coverage

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]

Date:   Wed, 2 Oct 2019 17:43:45 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     John Garry <john.garry@...wei.com>
Cc:     Wei Xu <xuwei5@...ilicon.com>, Linuxarm <linuxarm@...wei.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Bjorn Helgaas <bhelgaas@...gle.com>,
        Olof Johansson <olof@...om.net>
Subject: Re: [PATCH 3/3] bus: hisi_lpc: Expand build test coverage

On Tue, Oct 1, 2019 at 6:07 PM John Garry <john.garry@...wei.com> wrote:
>
> Currently the driver will only ever be built for ARM64 because it selects
> CONFIG_INDIRECT_PIO, which itself depends on ARM64.
>
> Expand build test coverage for the driver to other architectures by only
> selecting CONFIG_INDIRECT_PIO for ARM64, when we really want it.
>
> Signed-off-by: John Garry <john.garry@...wei.com>

Good idea, but doesn't this cause a link failure against
logic_pio_register_range() when INDIRECT_PIO is disabled?

      Arnd