linux-kernel - Re: [PATCH] RFC: Do not enable the v1 uAPI by default

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]

Message-ID: <CAMRc=McZGW698rCECoNGw32mroT=_cNtFTpE4XN_zbHDY81ibA@mail.gmail.com>
Date:   Mon, 6 Nov 2023 09:20:30 +0100
From:   Bartosz Golaszewski <brgl@...ev.pl>
To:     Linus Walleij <linus.walleij@...aro.org>,
        Phil Howard <phil@...getoid.com>
Cc:     Kent Gibson <warthog618@...il.com>,
        Andy Shevchenko <andy@...nel.org>, linux-gpio@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] RFC: Do not enable the v1 uAPI by default

On Sun, Nov 5, 2023 at 4:39 PM Linus Walleij <linus.walleij@...aro.org> wrote:
>
> On Sun, Nov 5, 2023 at 2:12 AM Kent Gibson <warthog618@...il.com> wrote:
>
> > If you want to provide the end user with two years to migrate, and given
> > that libgpiod is the major consumer, you might want to hold off for
> > another year.
>
> OK then, just testing the waters.
>
> Probably we need to encourage libgpiod 2.x a bit.
>

Thanks to Phil Howard's work on python bindings, they should soon be
more widely adopted. They are now the first thing that pops up in
google when searching for "libgpiod python" and now have a proper
homepage in pypi. Running 'pip3 install gpiod' will now work on
systems with no libgpiod installed too as it's vendored with libgpiod
v2.1 sources. I also plan to finally get around to using breathe and
exhale to produce proper sphinx docs. So hopefully we'll start getting
traction soon.

Bart