linux-kernel - Re: [PATCH v5 00/20] gpio: cdev: add uAPI v2

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:   Thu, 27 Aug 2020 18:02:03 +0200
From:   Bartosz Golaszewski <bgolaszewski@...libre.com>
To:     Linus Walleij <linus.walleij@...aro.org>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:     Kent Gibson <warthog618@...il.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>
Subject: Re: [PATCH v5 00/20] gpio: cdev: add uAPI v2

On Thu, Aug 27, 2020 at 5:53 PM Linus Walleij <linus.walleij@...aro.org> wrote:
>
> On Thu, Aug 27, 2020 at 4:00 PM Kent Gibson <warthog618@...il.com> wrote:
>
> > This patchset defines and implements a new version of the
> > GPIO CDEV uAPI to address existing 32/64-bit alignment issues, add
> > support for debounce, event sequence numbers, and allow for requested
> > lines with different configurations.
> > It provides some future proofing by adding optional configuration fields
> > and padding reserved for future use.
> >
> > The series can be partitioned into three blocks; the first two patches
> > are minor fixes that impact later patches, the next eleven contain the
> > v2 uAPI definition and implementation, and the final seven port the GPIO
> > tools to the v2 uAPI and extend them to use new uAPI features.
> >
> > The more complicated patches include their own commentary where
> > appropriate.
>
> I'm ready to queue this now. Certainly any remaining snags can be
> fixed in-tree.
>
> It kind of keeps in tradition with proper software projects "plan to
> throw one away" which is what we have traditionally done several
> times: the first Bluetooh framework was tossed, JFFS was tossed
> for JFFS2, Video4Linux was tossed for V4L2. So let's do this.
>
> Anyone against? I will put it on an immutable branch and then merge
> that in for devel.
>

Hi Linus,

please hold it maybe for one more week - I'd love to have some more
people take a look at the user facing header at least. Andy is usually
very thorough in his reviews so I'm Ccing him here.

I'll too skim through the series one more time.

Bart