From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Khem Raj <raj.khem@gmail.com>,
Armin Kuster <akuster808@gmail.com>,
openembedded-devel@lists.openembedded.org
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [meta-oe][PATCH] libgpiod: update v1.4.1 -> v1.4.2
Date: Wed, 29 Jan 2020 10:59:01 +0100 [thread overview]
Message-ID: <20200129095901.18965-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
While the v1.5 version of libgpiod has already been released - we can't
integrate it in yocto yet as it requires v5.5 linux kernel headers to
build. In the meantime - update the recipe to build the latest bug-fix
release from the v1.4.x branch.
Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
---
.../libgpiod/{libgpiod_1.4.1.bb => libgpiod_1.4.2.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta-oe/recipes-support/libgpiod/{libgpiod_1.4.1.bb => libgpiod_1.4.2.bb} (80%)
diff --git a/meta-oe/recipes-support/libgpiod/libgpiod_1.4.1.bb b/meta-oe/recipes-support/libgpiod/libgpiod_1.4.2.bb
similarity index 80%
rename from meta-oe/recipes-support/libgpiod/libgpiod_1.4.1.bb
rename to meta-oe/recipes-support/libgpiod/libgpiod_1.4.2.bb
index 0391deb86..bad88a54e 100644
--- a/meta-oe/recipes-support/libgpiod/libgpiod_1.4.1.bb
+++ b/meta-oe/recipes-support/libgpiod/libgpiod_1.4.2.bb
@@ -2,8 +2,8 @@ require libgpiod.inc
DEPENDS += "autoconf-archive-native"
-SRC_URI[md5sum] = "585b4bb431f99c4ba9b3ee58b9d494c1"
-SRC_URI[sha256sum] = "21ae8fd1f8dafc2eb2ba50e652390cf533d21351419a7426255895cb52e21b1c"
+SRC_URI[md5sum] = "b552bfa87685dfd728a1485e914bfae2"
+SRC_URI[sha256sum] = "b289b70e3d63a8e06205f7445d5342f4742277c267ce24a7c4d0017fff339e41"
# enable cxx bindings
PACKAGECONFIG ?= "cxx"
--
2.19.1
reply other threads:[~2020-01-30 12:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200129095901.18965-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=akuster808@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@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 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.