All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Kent Gibson <warthog618@gmail.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [libgpiod][PATCH] core: Basic port to uAPI v2
Date: Mon, 5 Oct 2020 12:27:11 +0200	[thread overview]
Message-ID: <CAMpxmJW+u35TYBiNru=bSJvuC+XJJos9zKqpgeG41u_hbaMjAA@mail.gmail.com> (raw)
In-Reply-To: <20201002160636.GA117143@sol>

On Fri, Oct 2, 2020 at 6:06 PM Kent Gibson <warthog618@gmail.com> 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@gmail.com> 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]

  reply	other threads:[~2020-10-05 10:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02  6:31 [libgpiod][PATCH] core: Basic port to uAPI v2 Kent Gibson
2020-10-02 13:48 ` Andy Shevchenko
2020-10-02 16:06   ` Kent Gibson
2020-10-05 10:27     ` Bartosz Golaszewski [this message]
2020-10-12 10:37 ` Bartosz Golaszewski
2020-10-13  7:08 ` Bartosz Golaszewski
2020-10-13  8:30   ` Kent Gibson
2020-10-14  3:17   ` Kent Gibson
2020-10-14  7:37     ` Bartosz Golaszewski
2020-10-14  8:51       ` Kent Gibson
2020-10-14  8:52         ` Bartosz Golaszewski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMpxmJW+u35TYBiNru=bSJvuC+XJJos9zKqpgeG41u_hbaMjAA@mail.gmail.com' \
    --to=bgolaszewski@baylibre.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=warthog618@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.