linux-kernel - Re: [PATCH 0/3] gpio: davinci: Redesign driver to accommodate ngpios in one gpio chip

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <9681e3d1-b769-286c-82e7-6cff85707c9e@ti.com>
Date:   Tue, 17 Jan 2017 21:44:08 +0530
From:   Keerthy <j-keerthy@...com>
To:     Linus Walleij <linus.walleij@...aro.org>
CC:     Tero Kristo <t-kristo@...com>,
        "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Alexandre Courbot <gnurou@...il.com>,
        Grygorii Strashko <grygorii.strashko@...com>
Subject: Re: [PATCH 0/3] gpio: davinci: Redesign driver to accommodate ngpios
 in one gpio chip



On Tuesday 17 January 2017 08:22 PM, Linus Walleij wrote:
> On Wed, Jan 11, 2017 at 6:00 AM, Keerthy <j-keerthy@...com> wrote:
>
>> The Davinci GPIO driver is implemented to work with one monolithic
>> Davinci GPIO platform device which may have up to Y(144) gpios.
>
> I'm a bit confused by the different DaVinci series since there seem
> to be different series floating and I don't know what order to apply them,
> it fails for me.
>
> Can you:
>
> - Rebase *ALL* your DaVinci work on top of the "devel" branch in the
>   GPIO tree.
>
> - Repost *ALL* patches that should be applied, in one batch.
>
> - Include any accumulated ACKs etc.

:-)

I have already posted a consolidated v2:
http://www.spinics.net/lists/linux-gpio/msg19109.html

Then seems like patch 6/6 is not required. So i will be posting the 
final set with Grygorii's reviewed-by. You can directly pick the v3 set.

Thanks,
Keerthy


>
> Yours,
> Linus Walleij
>