All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben.hutchings@essensium.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [libgpiod] How stable is the v2 API?
Date: Tue, 13 Jul 2021 23:26:46 +0200	[thread overview]
Message-ID: <20210713212646.GA8031@cephalopod> (raw)
In-Reply-To: <CAHp75VdSVB4shmAO2Oww=UU_5pqR=W3JZ98ChjZwZaRZ9gbVdQ@mail.gmail.com>

On Tue, Jul 13, 2021 at 12:16:52PM +0300, Andy Shevchenko wrote:
> On Tue, Jul 13, 2021 at 12:09 AM Ben Hutchings
> <ben.hutchings@essensium.com> wrote:
> >
> > I'm working on a project that requires GPIO debouncing and is planned
> > to use libgpiod.  But debouncing is only available on the unreleased
> > next/libgpiod-2.0 branch.
> >
> > What we'd like to know is whether the current C API on that branch is
> > expected to change much before release.  I don't expect any commitment
> > to API or ABI stability, but it would be helpful to have some
> > indication of how much change is likely to be needed in a client that
> > is written for the current API.
> 
> I believe this is the right thread to discuss and influence if needed.
> 
> https://lore.kernel.org/linux-gpio/20210621191830.10628-1-brgl@bgdev.pl/T/#ma70b1ab80804c09644f4a018ff5eff10464b195a

Thanks.  I've actually seen that already.  I don't think I need to
exert any "influence" as the current v2 API seems to do cover our
needs.

Ben.


  parent reply	other threads:[~2021-07-13 21:26 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 [this message]
2021-07-13 20:10 ` Bartosz Golaszewski
2021-07-13 21:46   ` Ben Hutchings
2021-07-15  8:31     ` 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=20210713212646.GA8031@cephalopod \
    --to=ben.hutchings@essensium.com \
    --cc=andy.shevchenko@gmail.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.