From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Koen Kooi <koen@dominion.thruhere.net>,
Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH 0/3] libgpiod: support for v1.0 series
Date: Fri, 23 Mar 2018 12:07:16 +0100 [thread overview]
Message-ID: <20180323110719.1010-1-brgl@bgdev.pl> (raw)
I recently released a new major version of libgpiod in which the
initial API was heavily reworked. Since it's no longer compatible
with v0.3.2 but I know there are users of the latter and I also
intend on supporting it for some time, I thought we should have both
versions in recipes-support.
This series adds a new recipe for libgpiod v1.0 that can live next to
v0.3.2.
Bartosz Golaszewski (3):
libgpiod: include the version in the recipe filename
libgpiod: split recipe into .inc and .bb files
libgpiod: add support for v1.x series
meta-oe/recipes-support/libgpiod/{libgpiod.bb => libgpiod.inc} | 5 -----
meta-oe/recipes-support/libgpiod/libgpiod_0.3.2.bb | 4 ++++
meta-oe/recipes-support/libgpiod/libgpiod_1.0.bb | 4 ++++
3 files changed, 8 insertions(+), 5 deletions(-)
rename meta-oe/recipes-support/libgpiod/{libgpiod.bb => libgpiod.inc} (80%)
create mode 100644 meta-oe/recipes-support/libgpiod/libgpiod_0.3.2.bb
create mode 100644 meta-oe/recipes-support/libgpiod/libgpiod_1.0.bb
--
2.16.1
next reply other threads:[~2018-03-23 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 11:07 Bartosz Golaszewski [this message]
2018-03-23 11:07 ` [meta-oe][PATCH 1/3] libgpiod: include the version in the recipe filename Bartosz Golaszewski
2018-03-23 11:07 ` [meta-oe][PATCH 2/3] libgpiod: split recipe into .inc and .bb files Bartosz Golaszewski
2018-03-23 11:07 ` [meta-oe][PATCH 3/3] libgpiod: add support for v1.x series 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=20180323110719.1010-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=koen@dominion.thruhere.net \
--cc=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.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