Re: [libgpiod][PATCH] core: Basic port to uAPI v2

[Bartosz Golaszewski <bgolaszewski@xxxxxxxxxxxx>]

On Fri, Oct 2, 2020 at 6:06 PM Kent Gibson <warthog618@xxxxxxxxx> wrote:
>
> On Fri, Oct 02, 2020 at 04:48:02PM +0300, Andy Shevchenko wrote:
> > On Fri, Oct 2, 2020 at 9:32 AM Kent Gibson <warthog618@xxxxxxxxx> wrote:
> > >
> > > Port existing implementation from GPIO uAPI v1 to v2.
> > > The libgpiod external interface remains unchanged, only the internal
> > > implementation switches from uAPI v1 to v2.
> >
> > Cool!
> >
>
> Not terribly - I needed a libgpiod-based testbed for my kernel
> changes, and this was the easiest way to do it.
> By happy coincidence that aligns with the path Bart wants to take for
> libgpiod 2.0, so here we are.
>

Indeed. I'll apply this to a staging branch for now called
for-linux-v5.10-rc1 and once v5.10-rc1 is tagged, we'll apply it and
make this kernel version a requirement on the master branch. From
there, we'll work on designing the v2 library API. I'm not giving
myself any deadlines - let's just get it right and it'll be ready when
it's done.

As I explained in my other email: I explicitly want to break the API
and ABI to improve the user-space interface. The question now is just
how to handle this. I'm in favor of keeping the library name as is and
keep the public header in the same place as well. I'm not too
concerned with two versions of the library living in the same system
really. I don't think this library is big or significant enough to
warrant dealing with versioning hell.

Bartosz

[snip]