All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anuj Mittal <anuj.mittal@intel.com>
To: mingli.yu@windriver.com, openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] bonnie++: Upgrade to 1.04
Date: Mon, 16 Jul 2018 15:11:15 +0800	[thread overview]
Message-ID: <ee78bb47-93a1-c8c3-5ab6-2cd9bdae0d17@intel.com> (raw)
In-Reply-To: <20180716053602.14820-1-mingli.yu@windriver.com>

On 07/16/2018 01:36 PM, mingli.yu@windriver.com wrote:
> From: Mingli Yu <mingli.yu@windriver.com>
> 
> Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
> ---
>  .../bonnie/{bonnie++_1.03e.bb => bonnie++_1.04.bb}         | 7 +++----
>  1 file changed, 3 insertions(+), 4 deletions(-)
>  rename meta-oe/recipes-benchmark/bonnie/{bonnie++_1.03e.bb => bonnie++_1.04.bb} (73%)
> 
> diff --git a/meta-oe/recipes-benchmark/bonnie/bonnie++_1.03e.bb b/meta-oe/recipes-benchmark/bonnie/bonnie++_1.04.bb
> similarity index 73%
> rename from meta-oe/recipes-benchmark/bonnie/bonnie++_1.03e.bb
> rename to meta-oe/recipes-benchmark/bonnie/bonnie++_1.04.bb
> index 2c1217e34..d7583f076 100644
> --- a/meta-oe/recipes-benchmark/bonnie/bonnie++_1.03e.bb
> +++ b/meta-oe/recipes-benchmark/bonnie/bonnie++_1.04.bb
> @@ -4,11 +4,10 @@ SECTION = "benchmark/tests"
>  LICENSE = "GPLv2"
>  LIC_FILES_CHKSUM = "file://copyright.txt;md5=cd4dde95a6b9d122f0a9150ae9cc3ee0"
>  
> -SRC_URI = "http://www.coker.com.au/bonnie++/${BPN}-${PV}.tgz \
> -           file://gcc-4.3-fixes.patch \
> +SRC_URI = "http://www.coker.com.au/bonnie++/${BPN}_${PV}.tgz \
>  "

Should the patch file itself be deleted too?

Thanks,

Anuj


  reply	other threads:[~2018-07-16  7:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16  5:36 [meta-oe][PATCH] bonnie++: Upgrade to 1.04 mingli.yu
2018-07-16  7:11 ` Anuj Mittal [this message]
2018-07-16  9:12   ` Yu, Mingli
2018-07-17  3:29     ` 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=ee78bb47-93a1-c8c3-5ab6-2cd9bdae0d17@intel.com \
    --to=anuj.mittal@intel.com \
    --cc=mingli.yu@windriver.com \
    --cc=openembedded-devel@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.