linux-kernel - Re: [PATCH] gpio: fix build failure: gpiochip

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: <c917f7f2-2f3b-f01e-8ea2-858eaf5f3e2d@nvidia.com>
Date:   Wed, 11 Sep 2019 00:39:48 +0100
From:   John Hubbard <jhubbard@...dia.com>
To:     Linus Walleij <linus.walleij@...aro.org>
CC:     YueHaibing <yuehaibing@...wei.com>,
        Bartosz Golaszewski <bgolaszewski@...libre.com>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] gpio: fix build failure: gpiochip_[un]lock*()
 static/non-static

On 9/8/19 12:16 AM, Linus Walleij wrote:
> On Sat, Sep 7, 2019 at 2:05 AM John Hubbard <jhubbard@...dia.com> wrote:
> 
>> While building with !CONFIG_GPIOLIB, I experienced a build failure,
>> because driver.h in that configuration supplies both a static and
>> a non-static version of these routines:
> 
> I think this is fixed in my latest version of the "devel" branch?
> 

OK, sounds good to me. Sorry for not spotting that a fix is in
the pipeline. :)


thanks,
-- 
John Hubbard
NVIDIA