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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 12 Mar 2020 15:21:34 +0100
From:   Linus Walleij <>
To:     Geert Uytterhoeven <>
Cc:     Bartosz Golaszewski <>,
        Jonathan Corbet <>,
        Harish Jenny K N <>,
        Eugeniu Rosca <>,
        Alexander Graf <>,
        Peter Maydell <>,
        Paolo Bonzini <>,
        Phil Reid <>,
        Marc Zyngier <>,
        Christoffer Dall <>,
        Magnus Damm <>,
        Rob Herring <>,
        Mark Rutland <>,
        "open list:GPIO SUBSYSTEM" <>,
        Linux Doc Mailing List <>,
        Linux-Renesas <>,
        "" <>,
        QEMU Developers <>
Subject: Re: [PATCH v5 2/5] gpiolib: Add support for GPIO line table lookup

Hi Geert,

I'm sorry for the slow review, it's a large patch set and
takes some time to sit down and review, and see whether my
earlier comments have been addressed.

On Tue, Feb 18, 2020 at 4:18 PM Geert Uytterhoeven
<> wrote:

> Currently GPIOs can only be referred to by GPIO controller and offset in
> GPIO lookup tables.
> Add support for looking them up by line name.
> Rename gpiod_lookup.chip_label to gpiod_lookup.key, to make it clear
> that this field can have two meanings, and update the kerneldoc and
> GPIO_LOOKUP*() macros.
> Signed-off-by: Geert Uytterhoeven <>
> Reviewed-by: Ulrich Hecht <>
> Reviewed-by: Eugeniu Rosca <>
> Tested-by: Eugeniu Rosca <>

I will try to understand why this change is necessary to implement
the gpio aggregator (probablt I will comment that on the other
patches like "aha now I see it" or so, but it would help a lot if the
commit message
would state the technical reason to why we need to do this change,
like what it is that you want to do and why you cannot do it without
this change.

Linus Walleij

Powered by blists - more mailing lists