From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-gpio@vger.kernel.org
Subject: Re: [libgpiod][PATCH v3] core: implement v2.0 API
Date: Mon, 7 Jun 2021 12:59:50 +0800 [thread overview]
Message-ID: <20210607045950.GA18318@sol> (raw)
In-Reply-To: <20210604094100.30075-1-brgl@bgdev.pl>
On Fri, Jun 04, 2021 at 11:41:00AM +0200, Bartosz Golaszewski wrote:
> This is the bulk of changes for the core C library.
>
> The documentation has been extended to document the lifetime management
> of objects explictly.
>
> The concept of attributes has been removed - instead the translation from
> configuration options to kernel request happens at the time of the line
> request call and can only fail at this stage - the config mutators no
> longer return any value.
>
> If the caller has passed a config that is too complicated, the request
> function will set errno to E2BIG which stands for: "Argument list too
> long". If the caller has passed an invalid value to any of the line config
> mutators, the error will be returned at the time of making the request.
>
> The direction and edge options have been split from the former
> request_type.
>
> The objects are no longer reference counted and no longer can be the
> responsibility for their lifetime shared.
>
> There are many other minor tweaks everywhere.
>
> Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>
> ---
> Hi Kent,
>
> this is another iteration of the new API. This time there are no big
> changes, mostly just documentation and naming-convention tweaks.
>
> I will push it out to a semi-official next/libgpiod-v2.0 branch and any
> follow-up changes will be squashed into the v2.0 API there.
>
I haven't looked through all the code, but gpiod.h looks good to me, and
I'm sure any issues in the implementation will come out in the wash, so
go for it.
Cheers,
Kent.
prev parent reply other threads:[~2021-06-07 5:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 9:41 [libgpiod][PATCH v3] core: implement v2.0 API Bartosz Golaszewski
2021-06-07 4:59 ` Kent Gibson [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=20210607045950.GA18318@sol \
--to=warthog618@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).