From: <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] stress-ng: upgrade 0.15.06 -> 0.15.07
Date: Mon, 17 Apr 2023 16:07:57 +0800 [thread overview]
Message-ID: <1681718877-19480-5-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1681718877-19480-1-git-send-email-wangmy@fujitsu.com>
From: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../stress-ng/{stress-ng_0.15.06.bb => stress-ng_0.15.07.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-extended/stress-ng/{stress-ng_0.15.06.bb => stress-ng_0.15.07.bb} (94%)
diff --git a/meta/recipes-extended/stress-ng/stress-ng_0.15.06.bb b/meta/recipes-extended/stress-ng/stress-ng_0.15.07.bb
similarity index 94%
rename from meta/recipes-extended/stress-ng/stress-ng_0.15.06.bb
rename to meta/recipes-extended/stress-ng/stress-ng_0.15.07.bb
index 31cf2e8987..674c58a6a2 100644
--- a/meta/recipes-extended/stress-ng/stress-ng_0.15.06.bb
+++ b/meta/recipes-extended/stress-ng/stress-ng_0.15.07.bb
@@ -7,7 +7,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
SRC_URI = "git://github.com/ColinIanKing/stress-ng.git;protocol=https;branch=master \
"
-SRCREV = "f2a80e4fdba0aaf71d7d3687acb34e3827e68886"
+SRCREV = "83ab1d2d7e39d9accba9d6dd0cc567645bb21d92"
S = "${WORKDIR}/git"
DEPENDS = "coreutils-native libbsd"
--
2.34.1
next prev parent reply other threads:[~2023-04-17 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 8:07 [OE-core] [PATCH] parted: upgrade 3.5 -> 3.6 wangmy
2023-04-17 8:07 ` [OE-core] [PATCH] python3-dtschema: upgrade 2023.1 -> 2023.4 wangmy
2023-04-17 8:07 ` [OE-core] [PATCH] python3-packaging: upgrade 23.0 -> 23.1 wangmy
2023-04-17 8:07 ` [OE-core] [PATCH] python3-pytest: upgrade 7.2.2 -> 7.3.1 wangmy
2023-04-17 8:07 ` wangmy [this message]
2023-04-18 23:59 ` [OE-core] [PATCH] parted: upgrade 3.5 -> 3.6 Khem Raj
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=1681718877-19480-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