public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Fri, 09 Nov 2012 15:27:43 +0100	[thread overview]
Message-ID: <509D12DF.9000506@ahsoftware.de> (raw)
In-Reply-To: <CAFLxGvzKJBA7VtzvafBry874GCiwVVWxtcktdQ=7BcVT3K2E_A@mail.gmail.com>

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.

Regards,

Alexander

  reply	other threads:[~2012-11-09 14:29 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 [this message]
2012-11-21 16:18     ` Alexander Holler
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=509D12DF.9000506@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox