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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Tue, 17 Jan 2017 15:52:40 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Keerthy <j-keerthy@...com>
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 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.

Yours,
Linus Walleij