From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] lttng-modules: upgrade 2.13.2 -> 2.13.3
Date: Mon, 28 Mar 2022 17:52:53 +0800 [thread overview]
Message-ID: <1648461173-15770-5-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1648461173-15770-1-git-send-email-wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../lttng/{lttng-modules_2.13.2.bb => lttng-modules_2.13.3.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-kernel/lttng/{lttng-modules_2.13.2.bb => lttng-modules_2.13.3.bb} (94%)
diff --git a/meta/recipes-kernel/lttng/lttng-modules_2.13.2.bb b/meta/recipes-kernel/lttng/lttng-modules_2.13.3.bb
similarity index 94%
rename from meta/recipes-kernel/lttng/lttng-modules_2.13.2.bb
rename to meta/recipes-kernel/lttng/lttng-modules_2.13.3.bb
index 86e0931af2..b6f8ac1315 100644
--- a/meta/recipes-kernel/lttng/lttng-modules_2.13.2.bb
+++ b/meta/recipes-kernel/lttng/lttng-modules_2.13.3.bb
@@ -13,7 +13,7 @@ SRC_URI = "https://lttng.org/files/${BPN}/${BPN}-${PV}.tar.bz2"
# Use :append here so that the patch is applied also when using devupstream
SRC_URI:append = " file://0001-src-Kbuild-change-missing-CONFIG_TRACEPOINTS-to-warn.patch"
-SRC_URI[sha256sum] = "dfd547d9041c8c545ae5b7bfef3f0ef2d9f2520d6ab44188c9ea8de56d5d298a"
+SRC_URI[sha256sum] = "7cf1acbb50b84116acc9b4281b81dcc2643d6018bbd1e8514ad1270239896c4b"
export INSTALL_MOD_DIR="kernel/lttng-modules"
--
2.25.1
prev parent reply other threads:[~2022-03-28 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 9:52 [OE-core] [PATCH] glib-networking: upgrade 2.70.1 -> 2.72.0 Wang Mingyu
2022-03-28 9:52 ` [OE-core] [PATCH] iproute2: upgrade 5.16.0 -> 5.17.0 Wang Mingyu
2022-03-28 9:52 ` [OE-core] [PATCH] libevdev: upgrade 1.12.0 -> 1.12.1 Wang Mingyu
2022-03-28 9:52 ` [OE-core] [PATCH] libsoup: upgrade 3.0.4 -> 3.0.5 Wang Mingyu
2022-03-28 9:52 ` Wang Mingyu [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=1648461173-15770-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