From: Anuj Mittal <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/2] libva-utils: upgrade 2.1.0 -> 2.2.0
Date: Fri, 13 Jul 2018 10:39:44 +0800 [thread overview]
Message-ID: <20180713023944.23722-2-anuj.mittal@intel.com> (raw)
In-Reply-To: <20180713023944.23722-1-anuj.mittal@intel.com>
* Add vainfo support in Android
* Remove driver specific test cases
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
---
.../libva/{libva-utils_2.1.0.bb => libva-utils_2.2.0.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-graphics/libva/{libva-utils_2.1.0.bb => libva-utils_2.2.0.bb} (89%)
diff --git a/meta/recipes-graphics/libva/libva-utils_2.1.0.bb b/meta/recipes-graphics/libva/libva-utils_2.2.0.bb
similarity index 89%
rename from meta/recipes-graphics/libva/libva-utils_2.1.0.bb
rename to meta/recipes-graphics/libva/libva-utils_2.2.0.bb
index a8018ea728..e35085cb98 100644
--- a/meta/recipes-graphics/libva/libva-utils_2.1.0.bb
+++ b/meta/recipes-graphics/libva/libva-utils_2.2.0.bb
@@ -15,8 +15,8 @@ LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://COPYING;md5=b148fc8adf19dc9aec17cf9cd29a9a5e"
SRC_URI = "https://github.com/intel/${BPN}/releases/download/${PV}/${BP}.tar.bz2"
-SRC_URI[md5sum] = "6649be70390606651cb636320bfd43c6"
-SRC_URI[sha256sum] = "f6a7790c3dcc56537372c90a83036a3136194a8b397e84e97bf9cc9254fa2c51"
+SRC_URI[md5sum] = "93b58aa5b14c16f4bace8a45dc255ec9"
+SRC_URI[sha256sum] = "ed7a6ed1fab657df4e83ea11f90310efcf31c27828f32d65351a28ca3c404dc0"
UPSTREAM_CHECK_URI = "https://github.com/intel/libva-utils/releases"
--
2.17.1
prev parent reply other threads:[~2018-07-13 2:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 2:39 [PATCH 1/2] libva: upgrade 2.1.0 -> 2.2.0 Anuj Mittal
2018-07-13 2:39 ` Anuj Mittal [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=20180713023944.23722-2-anuj.mittal@intel.com \
--to=anuj.mittal@intel.com \
--cc=openembedded-core@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