All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Ben Hutchings <ben.hutchings@essensium.com>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [libgpiod] How stable is the v2 API?
Date: Thu, 15 Jul 2021 10:31:53 +0200	[thread overview]
Message-ID: <CAMRc=Md3YUHSUGOjmNfZxDqJjBp4Rwnc9ROhqbMh7uPGJFy+eQ@mail.gmail.com> (raw)
In-Reply-To: <20210713214651.GB8031@cephalopod>

On Tue, Jul 13, 2021 at 11:46 PM Ben Hutchings
<ben.hutchings@essensium.com> wrote:
>
> On Tue, Jul 13, 2021 at 10:10:12PM +0200, Bartosz Golaszewski wrote:
> [...]
> > While - as you already assumed - there are no commitments to any API &
> > ABI stability yet, the interface should not change very much. I have a
> > single set of API changes in my queue that we discussed while
> > reviewing the C++ bindings and I don't expect there to be many more
> > coming after that.
>
> Is that single set of API changes the same as
> <https://patchwork.ozlabs.org/project/linux-gpio/list/?series=250005>
> or do you have more beyond that?
>

These have already been squashed with the top commit in the
next/libgpiod-2.0 branch (except for the last one). I have two more
that I will try to send out today. I'll Cc you.

Bart

> > Again: this is an estimation, not a promise.
>
> Understood.
>
> Thanks,
>
> Ben.

      reply	other threads:[~2021-07-15  8:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-12 21:08 [libgpiod] How stable is the v2 API? Ben Hutchings
2021-07-13  9:16 ` Andy Shevchenko
2021-07-13  9:20   ` Andy Shevchenko
2021-07-13 21:26   ` Ben Hutchings
2021-07-13 20:10 ` Bartosz Golaszewski
2021-07-13 21:46   ` Ben Hutchings
2021-07-15  8:31     ` Bartosz Golaszewski [this message]

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='CAMRc=Md3YUHSUGOjmNfZxDqJjBp4Rwnc9ROhqbMh7uPGJFy+eQ@mail.gmail.com' \
    --to=brgl@bgdev.pl \
    --cc=ben.hutchings@essensium.com \
    --cc=linux-gpio@vger.kernel.org \
    /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.