From: "Dan Murphy" <dmurphy@ti.com>
To: <richard.purdie@linuxfoundation.org>,
<openembedded-core@lists.openembedded.org>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>, Dan Murphy <dmurphy@ti.com>
Subject: [dunfell] [PATCH 2/2] lz4: upgrade 1.9.2 -> 1.9.3
Date: Wed, 9 Dec 2020 13:21:11 -0600 [thread overview]
Message-ID: <20201209192111.21817-2-dmurphy@ti.com> (raw)
In-Reply-To: <20201209192111.21817-1-dmurphy@ti.com>
From: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
---
meta/recipes-support/lz4/{lz4_1.9.2.bb => lz4_1.9.3.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-support/lz4/{lz4_1.9.2.bb => lz4_1.9.3.bb} (90%)
diff --git a/meta/recipes-support/lz4/lz4_1.9.2.bb b/meta/recipes-support/lz4/lz4_1.9.3.bb
similarity index 90%
rename from meta/recipes-support/lz4/lz4_1.9.2.bb
rename to meta/recipes-support/lz4/lz4_1.9.3.bb
index 455d2a5141f0..00f2dd32fedd 100644
--- a/meta/recipes-support/lz4/lz4_1.9.2.bb
+++ b/meta/recipes-support/lz4/lz4_1.9.3.bb
@@ -9,9 +9,9 @@ LIC_FILES_CHKSUM = "file://lib/LICENSE;md5=ebc2ea4814a64de7708f1571904b32cc \
PE = "1"
-SRCREV = "fdf2ef5809ca875c454510610764d9125ef2ebbd"
+SRCREV = "d44371841a2f1728a3f36839fd4b7e872d0927d3"
-SRC_URI = "git://github.com/lz4/lz4.git;branch=dev \
+SRC_URI = "git://github.com/lz4/lz4.git;branch=release \
file://run-ptest \
"
UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>.*)"
--
2.29.2
next prev parent reply other threads:[~2020-12-09 19:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 19:21 [dunfell] [PATCH 1/2] lz4: Use the new branch naming from upstream Dan Murphy
2020-12-09 19:21 ` Dan Murphy [this message]
2020-12-09 19:55 ` [OE-core] [dunfell] [PATCH 2/2] lz4: upgrade 1.9.2 -> 1.9.3 Steve Sakoman
2020-12-09 20:03 ` Dan Murphy
2020-12-09 20:23 ` Steve Sakoman
2020-12-09 20:49 ` Dan Murphy
2020-12-10 0:29 ` Steve Sakoman
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=20201209192111.21817-2-dmurphy@ti.com \
--to=dmurphy@ti.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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