public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: wangmy@fujitsu.com
To: openembedded-core@lists.openembedded.org
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] libva: upgrade 2.18.0 -> 2.19.0
Date: Mon, 17 Jul 2023 17:10:09 +0800	[thread overview]
Message-ID: <1689585025-23731-3-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1689585025-23731-1-git-send-email-wangmy@fujitsu.com>

From: Wang Mingyu <wangmy@fujitsu.com>

Changelog:
===========
* docs: fix references and descriptions snf focyhrn mstkup
* ci: add build docs test
* win: change default driver search path to bindir
* win: rely on compiler to define link names
* add: Add mono_chrome to VAEncSequenceParameterBufferAV1
* add: Enable support for license acquisition of multiple protected playbacks
* fix: year for version 2.18.0 in NEWS
* fix: use secure_getenv instead of getenv
* trace: Improve and add VA trace log for AV1 encode
* trace: Unify va log message, replace va_TracePrint with va_TraceMsg.

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
 meta/recipes-graphics/libva/libva.inc                           | 2 +-
 .../recipes-graphics/libva/{libva_2.18.0.bb => libva_2.19.0.bb} | 0
 2 files changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/libva/{libva_2.18.0.bb => libva_2.19.0.bb} (100%)

diff --git a/meta/recipes-graphics/libva/libva.inc b/meta/recipes-graphics/libva/libva.inc
index 7ed0c9ed89..3388fea32b 100644
--- a/meta/recipes-graphics/libva/libva.inc
+++ b/meta/recipes-graphics/libva/libva.inc
@@ -18,7 +18,7 @@ LICENSE = "MIT"
 
 SRC_URI = "${GITHUB_BASE_URI}/download/${PV}/libva-${PV}.tar.bz2"
 LIC_FILES_CHKSUM = "file://COPYING;md5=2e48940f94acb0af582e5ef03537800f"
-SRC_URI[sha256sum] = "a3577eeba0c23924686c7e2f2030073736c8282a80f27b5473e33ea94ccd4982"
+SRC_URI[sha256sum] = "963be798d559df7feebda6fa81aa0dae6f9409c633a37909c44c6aa8af1e2174"
 
 S = "${WORKDIR}/libva-${PV}"
 
diff --git a/meta/recipes-graphics/libva/libva_2.18.0.bb b/meta/recipes-graphics/libva/libva_2.19.0.bb
similarity index 100%
rename from meta/recipes-graphics/libva/libva_2.18.0.bb
rename to meta/recipes-graphics/libva/libva_2.19.0.bb
-- 
2.34.1



  parent reply	other threads:[~2023-07-17  9:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17  9:10 [OE-core] [PATCH] harfbuzz: upgrade 7.3.0 -> 8.0.1 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] libproxy: upgrade 0.5.2 -> 0.5.3 wangmy
2023-07-17  9:10 ` wangmy [this message]
2023-07-18  6:55   ` [OE-core] [PATCH] libva: upgrade 2.18.0 -> 2.19.0 Mittal, Anuj
2023-07-17  9:10 ` [OE-core] [PATCH] nghttp2: upgrade 1.54.0 -> 1.55.1 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] debianutils: upgrade 5.7 -> 5.8 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] glib-2.0: upgrade 2.76.3 -> 2.76.4 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] python3-pip: upgrade 23.1.2 -> 23.2 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] python3-zipp: upgrade 3.15.0 -> 3.16.2 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] opkg: upgrade 0.6.1 -> 0.6.2 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] opkg-utils: upgrade 0.5.0 " wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] python3-cryptography-vectors: upgrade 41.0.1 -> 41.0.2 wangmy
2023-07-17  9:31   ` Tim Orling
2023-07-17  9:10 ` [OE-core] [PATCH] python3-editables: upgrade 0.3 -> 0.4 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] python3-git: upgrade 3.1.31 -> 3.1.32 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] python3-hypothesis: upgrade 6.80.0 -> 6.81.2 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] python3-importlib-metadata: upgrade 6.7.0 -> 6.8.0 wangmy
2023-07-17 10:10   ` Tim Orling
2023-07-17  9:10 ` [OE-core] [PATCH] python3-jsonschema: upgrade 4.17.3 -> 4.18.3 wangmy
2023-07-19 22:50   ` Alexandre Belloni
2023-07-17  9:10 ` [OE-core] [PATCH] python3-numpy: upgrade 1.25.0 -> 1.25.1 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] python3-typing-extensions: upgrade 4.7.0 -> 4.7.1 wangmy
2023-07-17  9:10 ` [OE-core] [PATCH] repo: upgrade 2.34.1 -> 2.35 wangmy

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=1689585025-23731-3-git-send-email-wangmy@fujitsu.com \
    --to=wangmy@fujitsu.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