From: Wang Mingyu < wangmy@fujitsu.com>
To: openembedded-core@lists.openembedded.org
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH 19/23] spirv-llvm-translator: upgrade 21.1.3 -> 21.1.5
Date: Tue, 3 Mar 2026 18:09:24 +0800 [thread overview]
Message-ID: <20260303100929.1624-19-wangmy@fujitsu.com> (raw)
In-Reply-To: <20260303100929.1624-1-wangmy@fujitsu.com>
From: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
...lvm-translator_21.1.3.bb => spirv-llvm-translator_21.1.5.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/spir/{spirv-llvm-translator_21.1.3.bb => spirv-llvm-translator_21.1.5.bb} (94%)
diff --git a/meta/recipes-graphics/spir/spirv-llvm-translator_21.1.3.bb b/meta/recipes-graphics/spir/spirv-llvm-translator_21.1.5.bb
similarity index 94%
rename from meta/recipes-graphics/spir/spirv-llvm-translator_21.1.3.bb
rename to meta/recipes-graphics/spir/spirv-llvm-translator_21.1.5.bb
index f8a7b8f32e..a727079a43 100644
--- a/meta/recipes-graphics/spir/spirv-llvm-translator_21.1.3.bb
+++ b/meta/recipes-graphics/spir/spirv-llvm-translator_21.1.5.bb
@@ -6,7 +6,7 @@ LIC_FILES_CHKSUM = "file://LICENSE.TXT;md5=47e311aa9caedd1b3abf098bd7814d1d"
# pattern: llvm_branch_200, currently there are no minor releases, so, no llvm_branch_201
SPIRV_BRANCH = "llvm_release_${@oe.utils.trim_version('${PV}', 1).replace('.', '')}0"
-SRCREV = "a79c852b36785588032a2dd7c39aa15ec4d24b20"
+SRCREV = "a76fd0702de564476fb31e8a15f1415f05ad8951"
SRC_URI = " \
git://github.com/KhronosGroup/SPIRV-LLVM-Translator;protocol=https;tag=v${PV};branch=${SPIRV_BRANCH} \
"
--
2.43.0
next prev parent reply other threads:[~2026-03-03 10:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 10:09 [OE-core] [PATCH 01/23] ccache: upgrade 4.12.2 -> 4.12.3 Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 02/23] diffoscope: upgrade 311 -> 313 Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 03/23] ed: upgrade 1.22.4 -> 1.22.5 Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 04/23] enchant2: upgrade 2.8.14 -> 2.8.15 Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 05/23] fastfloat: upgrade 8.2.2 -> 8.2.3 Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 06/23] hwdata: upgrade 0.403 -> 0.404 Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 07/23] less: upgrade 691 -> 692 Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 08/23] libcap-ng-python,libcap-ng: upgrade 0.9 -> 0.9.1,0.9 -> 0.9.1 Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 09/23] libfontenc: upgrade 1.1.8 -> 1.1.9 Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 10/23] libgpg-error: upgrade 1.58 -> 1.59 Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 11/23] libsoup: upgrade 3.6.5 -> 3.6.6 Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 12/23] libtraceevent: upgrade 1.8.6 -> 1.9.0 Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 13/23] libuv: upgrade 1.51.0 -> 1.52.0 Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 14/23] libx11: upgrade 1.8.12 -> 1.8.13 Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 15/23] libxmlb: upgrade 0.3.24 -> 0.3.25 Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 16/23] p11-kit: upgrade 0.26.1 -> 0.26.2 Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 17/23] rpm-sequoia-crypto-policy: upgrade to latest revision Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 18/23] sbc: upgrade 2.1 -> 2.2 Wang Mingyu
2026-03-03 10:09 ` Wang Mingyu [this message]
2026-03-03 10:09 ` [OE-core] [PATCH 20/23] taglib: upgrade 2.1.1 " Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 21/23] ttyrun: upgrade 2.40.0 -> 2.41.0 Wang Mingyu
2026-03-03 10:09 ` [OE-core] [PATCH 22/23] vulkan-samples: upgrade to latest revision Wang Mingyu
2026-03-03 10:17 ` Patchtest results for " patchtest
2026-03-04 9:56 ` Alexander Kanavin
2026-03-03 10:09 ` [OE-core] [PATCH 23/23] xorgproto: upgrade 2024.1 -> 2025.1 Wang Mingyu
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=20260303100929.1624-19-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