From: Ferry Toth <fntoth@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Kent Gibson <warthog618@gmail.com>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [ANNOUNCE] libgpiod v2.0-rc1 released
Date: Wed, 8 Feb 2023 21:00:50 +0100 [thread overview]
Message-ID: <14de29ca-e9b5-101c-351d-156b21f4a3df@gmail.com> (raw)
In-Reply-To: <CAMRc=MdyS6CsMkyvRL+_Shr__QnYxXE_Di6DqRKvh+QB_A3Qgg@mail.gmail.com>
Op 08-02-2023 om 16:08 schreef Bartosz Golaszewski:
> There have been no issues raised since the RFC so let's get it out.
> I'm tagging a release candidate that I will also try and make
> available in meta-openembedded with the hope that it will get some
> exposure and testing before we commit to a final v2.0 release.
That is very good news.
I'd like to test this on Intel Edison-Arduino.
I guess the recipe for meta-openembedded will a -rc as well? Where can I
find it?
> The core C API as well as all the bindings and tools have been
> completely overhauled. There are too many changes to list them all
> here - please refer to NEWS and the docs as the library has been
> entirely rebuilt.
>
> Thanks again to Kent, Viresh and Andy for the hard work on designing,
> writing and testing the project.
>
> The release tarball[1] and git repo[2] are available on kernel.org
>
> Bart
>
> [1] https://mirrors.edge.kernel.org/pub/software/libs/libgpiod/
> [2] git://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git
next prev parent reply other threads:[~2023-02-08 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 15:08 [ANNOUNCE] libgpiod v2.0-rc1 released Bartosz Golaszewski
2023-02-08 20:00 ` Ferry Toth [this message]
2023-02-09 8:28 ` 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=14de29ca-e9b5-101c-351d-156b21f4a3df@gmail.com \
--to=fntoth@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=viresh.kumar@linaro.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 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).