linux-kernel - Re: [PATCH] gpio: Move gpiochip_.*lock_as

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: <CACRpkdZcfRnvSGGfpiR=Kb6TDJQjtcQJ4ikhaFC4oB8ZP35+aQ@mail.gmail.com>
Date:   Thu, 5 Sep 2019 11:36:14 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Yuehaibing <yuehaibing@...wei.com>
Cc:     Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
        Bartosz Golaszewski <bgolaszewski@...libre.com>,
        Alexandre Courbot <acourbot@...dia.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] gpio: Move gpiochip_.*lock_as_irq() to the proper ifdef

I aldready fixed this up in my tree.

On Thu, Sep 5, 2019 at 4:04 AM Yuehaibing <yuehaibing@...wei.com> wrote:

> Interesting, my patch indeed do the correct thing：

It is a classic merge collision. Something fun for the subsystem
maintainer to deal with :D

Yours,
Linus Walleij