From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V3] memtest86+: new package
Date: Sun, 1 Feb 2015 12:02:19 +0100 [thread overview]
Message-ID: <20150201120219.6f32addf@free-electrons.com> (raw)
In-Reply-To: <54CD6C81.1040808@ou.edu>
Dear Steve Kenton,
On Sat, 31 Jan 2015 18:00:01 -0600, Steve Kenton wrote:
> Memtest86+ is a bootable standalone memory test program.
>
> Please note that this is the forked memtest86+ program and not
> the original memtest86 which has different licensing. Buildroot
> does not support packages with a '+' sign in their name.
>
> Memtest86+ is a utility designed to test whether your memory
> is in working order. It repeatedly writes an enormous amount
> of different patterns to all memory locations and reads them
> back again and verifies whether the result of the read is the
> same as what was written to memory.
>
> Memtest86+ will only work on 32-bit or 64-bit x86 targets.
> It boots as an i486 program and autodetects hardware.
>
> Signed-off-by Stephen M. Kenton <skenton@ou.edu>
Reviewed-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> + Please note that this is the forked memtest86+ program and not
> + the original memtest86 which has different licensing. Buildroot
> + does not support packages with a '+' sign in their name.
This sentence could be improved:
Buildroot does not support packages with a '+' sign in their
name, which explains why it is named memtest86 and not
memtest86+.
I guess Peter can make the change when applying.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-02-01 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 0:00 [Buildroot] [PATCH V3] memtest86+: new package Steve Kenton
2015-02-01 11:02 ` Thomas Petazzoni [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=20150201120219.6f32addf@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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