From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] lttng-ust: upgrade 2.13.3 -> 2.13.4
Date: Tue, 30 Aug 2022 12:11:49 +0800 [thread overview]
Message-ID: <1661832712-12546-2-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1661832712-12546-1-git-send-email-wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../lttng/{lttng-ust_2.13.3.bb => lttng-ust_2.13.4.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-kernel/lttng/{lttng-ust_2.13.3.bb => lttng-ust_2.13.4.bb} (95%)
diff --git a/meta/recipes-kernel/lttng/lttng-ust_2.13.3.bb b/meta/recipes-kernel/lttng/lttng-ust_2.13.4.bb
similarity index 95%
rename from meta/recipes-kernel/lttng/lttng-ust_2.13.3.bb
rename to meta/recipes-kernel/lttng/lttng-ust_2.13.4.bb
index cc88bf5b11..56200ac3e1 100644
--- a/meta/recipes-kernel/lttng/lttng-ust_2.13.3.bb
+++ b/meta/recipes-kernel/lttng/lttng-ust_2.13.4.bb
@@ -34,7 +34,7 @@ SRC_URI = "https://lttng.org/files/lttng-ust/lttng-ust-${PV}.tar.bz2 \
file://0001-Makefile.am-update-rpath-link.patch \
"
-SRC_URI[sha256sum] = "2cc42f51145050430ac4ab72b32d95fd78d5566ccbe44e14a8fcdd23c0ed8f6f"
+SRC_URI[sha256sum] = "698f82ec5dc56e981c0bb08c46ebabaf31c60e877c2e365b9fd6d3a9fff8b398"
CVE_PRODUCT = "ust"
--
2.25.1
next prev parent reply other threads:[~2022-08-30 4:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 4:11 [OE-core] [PATCH] lttng-tools: upgrade 2.13.7 -> 2.13.8 Wang Mingyu
2022-08-30 4:11 ` Wang Mingyu [this message]
2022-08-30 4:11 ` [OE-core] [PATCH] mesa: upgrade 22.1.6 -> 22.1.7 Wang Mingyu
2022-08-30 20:16 ` Alexandre Belloni
2022-08-30 4:11 ` [OE-core] [PATCH] libatomic-ops: upgrade 7.6.12 -> 7.6.14 Wang Mingyu
2022-08-30 4:11 ` [OE-core] [PATCH] lz4: upgrade 1.9.3 -> 1.9.4 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=1661832712-12546-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