All of lore.kernel.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-utils: upgrade 2.17.0 -> 2.17.1
Date: Mon, 9 Jan 2023 13:14:55 +0800	[thread overview]
Message-ID: <1673241297-28966-2-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1673241297-28966-1-git-send-email-wangmy@fujitsu.com>

From: Wang Mingyu <wangmy@fujitsu.com>

Changelog:
==========
* fix: Fix possible memory leak
* fix: fix coding issues of array size and function return types

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
 .../libva/{libva-utils_2.17.0.bb => libva-utils_2.17.1.bb}      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/libva/{libva-utils_2.17.0.bb => libva-utils_2.17.1.bb} (95%)

diff --git a/meta/recipes-graphics/libva/libva-utils_2.17.0.bb b/meta/recipes-graphics/libva/libva-utils_2.17.1.bb
similarity index 95%
rename from meta/recipes-graphics/libva/libva-utils_2.17.0.bb
rename to meta/recipes-graphics/libva/libva-utils_2.17.1.bb
index c5a563b853..1e475e804b 100644
--- a/meta/recipes-graphics/libva/libva-utils_2.17.0.bb
+++ b/meta/recipes-graphics/libva/libva-utils_2.17.1.bb
@@ -15,7 +15,7 @@ LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://COPYING;md5=b148fc8adf19dc9aec17cf9cd29a9a5e"
 
 SRC_URI = "git://github.com/intel/libva-utils.git;branch=v2.17-branch;protocol=https"
-SRCREV = "42c02a6a37b1bfce91a7f15c898750f2ee9e3d6a"
+SRCREV = "3a291be22cfe70e41bad8a376fa278efa651fdff"
 S = "${WORKDIR}/git"
 
 UPSTREAM_CHECK_GITTAGREGEX = "(?P<pver>(\d+(\.\d+)+))$"
-- 
2.25.1



  reply	other threads:[~2023-01-09  5:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09  5:14 [OE-core] [PATCH] libsdl2: upgrade 2.26.1 -> 2.26.2 wangmy
2023-01-09  5:14 ` wangmy [this message]
2023-01-09  5:14 ` [OE-core] [PATCH] libxkbcommon: upgrade 1.4.1 -> 1.5.0 wangmy
2023-01-09  5:14 ` [OE-core] [PATCH] mpfr: upgrade 4.1.1 -> 4.2.0 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=1673241297-28966-2-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 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.