From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] vulkan-headers: upgrade 1.3.216.0 -> 1.3.225
Date: Tue, 30 Aug 2022 12:24:51 +0800 [thread overview]
Message-ID: <1661833494-12657-2-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1661833494-12657-1-git-send-email-wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/vulkan/{vulkan-headers_1.3.216.0.bb => vulkan-headers_1.3.225.bb} (93%)
--git a/meta/recipes-graphics/vulkan/vulkan-headers_1.3.216.0.bb b/meta/recipes-graphics/vulkan/vulkan-headers_1.3.225.bb
similarity index 93%
rename from meta/recipes-graphics/vulkan/vulkan-headers_1.3.216.0.bb
rename to meta/recipes-graphics/vulkan/vulkan-headers_1.3.225.bb
index 5f7917ae82..64b9ad22c8 100644
--- a/meta/recipes-graphics/vulkan/vulkan-headers_1.3.216.0.bb
+++ b/meta/recipes-graphics/vulkan/vulkan-headers_1.3.225.bb
@@ -11,7 +11,7 @@ LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=3b83ef96387f14655fc854ddc3c6bd57"
SRC_URI = "git://github.com/KhronosGroup/Vulkan-Headers.git;branch=main;protocol=https"
-SRCREV = "3ef4c97fd6ea001d75a8e9da408ee473c180e456"
+SRCREV = "715673702f5b18ffb8e5832e67cf731468d32ac6"
S = "${WORKDIR}/git"
--
2.25.1
next prev parent reply other threads:[~2022-08-30 4:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 4:24 [OE-core] [PATCH] python3-setuptools: upgrade 65.0.2 -> 65.3.0 Wang Mingyu
2022-08-30 4:24 ` Wang Mingyu [this message]
2022-08-30 7:05 ` [OE-core] [PATCH] vulkan-headers: upgrade 1.3.216.0 -> 1.3.225 Alexander Kanavin
2022-08-30 4:24 ` [OE-core] [PATCH] vulkan-loader: " Wang Mingyu
2022-08-30 4:24 ` [OE-core] [PATCH] vulkan-tools: " Wang Mingyu
2022-08-30 4:24 ` [OE-core] [PATCH] python3-hatchling: upgrade 1.8.0 -> 1.8.1 Wang Mingyu
2022-08-31 16:31 ` [OE-core] [PATCH] python3-setuptools: upgrade 65.0.2 -> 65.3.0 Alexandre Belloni
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=1661833494-12657-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox