From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] memtester: version bump 4.0.8 -> 4.3.0
Date: Mon, 23 Jun 2014 15:45:47 +0200 [thread overview]
Message-ID: <20140623134547.GJ16937@pengutronix.de> (raw)
In-Reply-To: <1403249588-4857-1-git-send-email-list-09_ptxdist@tqsc.de>
On Fri, Jun 20, 2014 at 09:33:08AM +0200, Markus Niebel wrote:
> From: Markus Niebel <Markus.Niebel@tq-group.com>
>
Thanks, applied.
Unrelated to this patch, but I noticed that the code is compiled without
optimization. Do you think it makes sense to add something like this to the
prepare stage:
@echo "CFLAGS = -O2 -g" >> $(MEMTESTER_DIR)/Makefile
Michael
> Signed-off-by: Markus Niebel <Markus.Niebel@tq-group.com>
>
> ---
> rules/memtester.make | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/rules/memtester.make b/rules/memtester.make
> index 8fd3dd7..e83a0b8 100644
> --- a/rules/memtester.make
> +++ b/rules/memtester.make
> @@ -17,8 +17,8 @@ PACKAGES-$(PTXCONF_MEMTESTER) += memtester
> #
> # Paths and names
> #
> -MEMTESTER_VERSION := 4.0.8
> -MEMTESTER_MD5 := a4971ed1ccaf5b2e2148fd66b0eb7363
> +MEMTESTER_VERSION := 4.3.0
> +MEMTESTER_MD5 := 598f41b7308e1f736164bca3ab84ddbe
> MEMTESTER := memtester-$(MEMTESTER_VERSION)
> MEMTESTER_SUFFIX := tar.gz
> MEMTESTER_URL := http://pyropus.ca/software/memtester/old-versions/$(MEMTESTER).$(MEMTESTER_SUFFIX)
> --
> 1.7.9.5
>
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-06-23 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 7:33 Markus Niebel
2014-06-23 13:45 ` Michael Olbrich [this message]
2014-06-24 13:12 ` Markus Niebel
2014-06-24 13:18 ` Michael Olbrich
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=20140623134547.GJ16937@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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