From: Alexander Holler <holler@ahsoftware.de>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: memtest: make it a bit faster
Date: Wed, 21 Nov 2012 17:18:07 +0100 [thread overview]
Message-ID: <50ACFEBF.4070906@ahsoftware.de> (raw)
In-Reply-To: <509D12DF.9000506@ahsoftware.de>
Hello,
Am 09.11.2012 15:27, schrieb Alexander Holler:
> Am 09.11.2012 15:21, schrieb richard -rw- weinberger:
>> On Fri, Nov 9, 2012 at 2:12 PM, Alexander Holler <holler@ahsoftware.de> wrote:
>>> While implementing the same functionality for arm, I've noticed that
>>> memtest does an unnecessary round to zero the memory. Just reversing the
>>> order so that the last round writes 0s spares that round.
>>>
>>> While there, I've also changed the message if bad memory is found from
>>> informational to emergency.
>>>
>>> And last I've removed some warnings from checkpatch.
>>
>> Please send these as additional patch.
>
> Than it might be better to wait for an answer from some ARM-people.
>
> Maybe it will make sense to move the whole file to mm/ or similar where
> I could be used and modified for usage by ARM too.
As I don't know if version for ARM (or the move) will ever happen, I've
now made 2 patches as requested. They will follow.
Regards,
Alexander
next prev parent reply other threads:[~2012-11-21 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 13:12 [PATCH] x86: memtest: make it a bit faster Alexander Holler
2012-11-09 14:21 ` richard -rw- weinberger
2012-11-09 14:27 ` Alexander Holler
2012-11-21 16:18 ` Alexander Holler [this message]
2012-11-21 16:24 ` [PATCH 1/2] x86: memtest: checkpatch and emergency warning if memtest fails Alexander Holler
2012-11-21 16:24 ` [PATCH 2/2] x86: memtest: remove unnecessary round to leave memtest with zeroed mem Alexander Holler
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=50ACFEBF.4070906@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
/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.