All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 12/20] stress-ng: upgrade 0.11.14 -> 0.11.15
Date: Thu, 16 Jul 2020 22:08:00 +0100	[thread overview]
Message-ID: <20200716210808.7438-12-richard.purdie@linuxfoundation.org> (raw)
In-Reply-To: <20200716210808.7438-1-richard.purdie@linuxfoundation.org>

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 .../stress-ng/{stress-ng_0.11.14.bb => stress-ng_0.11.15.bb}    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-extended/stress-ng/{stress-ng_0.11.14.bb => stress-ng_0.11.15.bb} (89%)

diff --git a/meta/recipes-extended/stress-ng/stress-ng_0.11.14.bb b/meta/recipes-extended/stress-ng/stress-ng_0.11.15.bb
similarity index 89%
rename from meta/recipes-extended/stress-ng/stress-ng_0.11.14.bb
rename to meta/recipes-extended/stress-ng/stress-ng_0.11.15.bb
index f1d91da2b48..8ea0476db5a 100644
--- a/meta/recipes-extended/stress-ng/stress-ng_0.11.14.bb
+++ b/meta/recipes-extended/stress-ng/stress-ng_0.11.15.bb
@@ -9,7 +9,7 @@ SRC_URI = "https://kernel.ubuntu.com/~cking/tarballs/${BPN}/${BP}.tar.xz \
            file://0001-Do-not-preserve-ownership-when-installing-example-jo.patch \
            file://no_daddr_t.patch \
            "
-SRC_URI[sha256sum] = "b21436fdbd9dc482a3fd95ae27cccf0097d0f226361ea3785215f7a4ad50136b"
+SRC_URI[sha256sum] = "6a333650fb5c85c5221f10d2cf890e9fc56530696e118d975fbbe96126c06963"
 
 DEPENDS = "coreutils-native"
 
-- 
2.25.1


  parent reply	other threads:[~2020-07-16 21:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 21:07 [PATCH 01/20] libuv: upgrade 1.38.0 -> 1.38.1 Richard Purdie
2020-07-16 21:07 ` [PATCH 02/20] btrfs-tools: upgrade 5.6.1 -> 5.7 Richard Purdie
2020-07-16 21:07 ` [PATCH 03/20] init-system-helpers: upgrade 1.57 -> 1.58 Richard Purdie
2020-07-16 21:07 ` [PATCH 04/20] createrepo-c: upgrade 0.15.11 -> 0.16.0 Richard Purdie
2020-07-16 21:07 ` [PATCH 05/20] mtd-utils: upgrade 2.1.1 -> 2.1.2 Richard Purdie
2020-07-16 21:07 ` [PATCH 06/20] dpkg: upgrade 1.20.0 -> 1.20.5 Richard Purdie
2020-07-16 21:07 ` [PATCH 07/20] python3-cython: upgrade 0.29.20 -> 0.29.21 Richard Purdie
2020-07-16 21:07 ` [PATCH 08/20] python3-git: upgrade 3.1.3 -> 3.1.7 Richard Purdie
2020-07-16 21:07 ` [PATCH 09/20] asciidoc: upgrade 9.0.0 -> 9.0.1 Richard Purdie
2020-07-16 21:07 ` [PATCH 10/20] libnsl2: upgrade 1.2.0 -> 1.3.0 Richard Purdie
2020-07-16 21:07 ` [PATCH 11/20] rpcsvc-proto: upgrade 1.4.1 -> 1.4.2 Richard Purdie
2020-07-16 21:08 ` Richard Purdie [this message]
2020-07-16 21:08 ` [PATCH 13/20] epiphany: upgrade 3.36.2 -> 3.36.3 Richard Purdie
2020-07-16 21:08 ` [PATCH 14/20] ffmpeg: upgrade 4.3 -> 4.3.1 Richard Purdie
2020-07-16 21:08 ` [PATCH 15/20] gnupg: upgrade 2.2.20 -> 2.2.21 Richard Purdie
2020-07-16 21:08 ` [PATCH 16/20] mpg123: upgrade 1.26.1 -> 1.26.2 Richard Purdie
2020-07-16 21:08 ` [PATCH 17/20] libevent: upgrade 2.1.11 -> 2.1.12 Richard Purdie
2020-07-16 21:08 ` [PATCH 18/20] webkitgtk: upgrade 2.28.2 -> 2.28.3 Richard Purdie
2020-07-16 21:08 ` [PATCH 19/20] libgcrypt: upgrade 1.8.5 -> 1.8.6 Richard Purdie
2020-07-16 21:08 ` [PATCH 20/20] mpfr: upgrade 4.0.2 -> 4.1.0 Richard Purdie

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=20200716210808.7438-12-richard.purdie@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.