From: <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [[oe] [meta-oe] [PATCH] tbb: upgrade 2021.8.0 -> 2021.9.0
Date: Mon, 17 Apr 2023 14:56:35 +0800 [thread overview]
Message-ID: <1681714595-18749-5-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1681714595-18749-1-git-send-email-wangmy@fujitsu.com>
From: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../recipes-support/tbb/{tbb_2021.8.0.bb => tbb_2021.9.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-oe/recipes-support/tbb/{tbb_2021.8.0.bb => tbb_2021.9.0.bb} (98%)
diff --git a/meta-oe/recipes-support/tbb/tbb_2021.8.0.bb b/meta-oe/recipes-support/tbb/tbb_2021.9.0.bb
similarity index 98%
rename from meta-oe/recipes-support/tbb/tbb_2021.8.0.bb
rename to meta-oe/recipes-support/tbb/tbb_2021.9.0.bb
index 5606d38da..028291c96 100644
--- a/meta-oe/recipes-support/tbb/tbb_2021.8.0.bb
+++ b/meta-oe/recipes-support/tbb/tbb_2021.9.0.bb
@@ -12,7 +12,7 @@ DEPENDS:append:libc-musl = " libucontext"
PE = "1"
BRANCH = "onetbb_2021"
-SRCREV = "c9497714821c3d443ee44c732609eb6850195ffb"
+SRCREV = "a00cc3b8b5fb4d8115e9de56bf713157073ed68c"
SRC_URI = "git://github.com/oneapi-src/oneTBB.git;protocol=https;branch=${BRANCH} \
file://0001-CMakeLists.txt-exclude-riscv64-riscv32.patch \
"
--
2.34.1
prev parent reply other threads:[~2023-04-17 6:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 6:56 [oe] [meta-python] [PATCH] python3-xlsxwriter: upgrade 3.0.9 -> 3.1.0 wangmy
2023-04-17 6:56 ` [oe] [meta-python] [PATCH] python3-zeroconf: upgrade 0.55.0 -> 0.56.0 wangmy
2023-04-17 6:56 ` [oe] [meta-oe] [PATCH] remmina: upgrade 1.4.29 -> 1.4.30 wangmy
2023-04-17 6:56 ` [oe] [meta-oe] [PATCH] sip: upgrade 6.7.7 -> 6.7.8 wangmy
2023-04-17 6:56 ` wangmy [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=1681714595-18749-5-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