From: Stefan Assmann <sassmann@kpanic.de>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-mm@kvack.org, tony.luck@intel.com, andi@firstfloor.org,
mingo@elte.hu, hpa@zytor.com, rick@vanrein.org,
akpm@linux-foundation.org
Subject: Re: [PATCH 3/3] Add documentation and credits for BadRAM
Date: Thu, 26 May 2011 08:39:37 +0200 [thread overview]
Message-ID: <4DDDF5A9.8060906@kpanic.de> (raw)
In-Reply-To: <20110524165543.3c31d9ea.rdunlap@xenotime.net>
On 25.05.2011 01:55, Randy Dunlap wrote:
> On Tue, 24 May 2011 13:20:48 +0200 Stefan Assmann wrote:
>> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
>> index cc85a92..ba3e984 100644
>> --- a/Documentation/kernel-parameters.txt
>> +++ b/Documentation/kernel-parameters.txt
>> @@ -51,6 +51,7 @@ parameter is applicable:
>> FB The frame buffer device is enabled.
>> GCOV GCOV profiling is enabled.
>> HW Appropriate hardware is enabled.
>> + HWPOISON Handling of memory pages reported as being corrupt
>
> These entries are normally used as in my example below. I'm not sure that
> it makes sense here.
>
>> IA-64 IA-64 architecture is enabled.
>> IMA Integrity measurement architecture is enabled.
>> IOSCHED More than one I/O scheduler is enabled.
>> @@ -373,6 +374,11 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
>>
>> autotest [IA64]
>>
>> + badram= When CONFIG_MEMORY_FAILURE is set, this parameter
>
> badram= [HWPOISON] When CONFIG_MEMORY_FAILURE is set, this parameter
New patch with spelling fixes and updated
Documentation/kernel-parameters.txt.
Thanks Randy.
Stefan
prev parent reply other threads:[~2011-05-26 6:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 11:20 [PATCH 0/3] support for broken memory modules (BadRAM) Stefan Assmann
2011-05-24 11:20 ` [PATCH 1/3] Add string parsing function get_next_ulong Stefan Assmann
2011-05-24 11:20 ` [PATCH 2/3] support for broken memory modules (BadRAM) Stefan Assmann
2011-05-24 11:20 ` [PATCH 3/3] Add documentation and credits for BadRAM Stefan Assmann
2011-05-24 23:55 ` Randy Dunlap
2011-05-26 6:39 ` Stefan Assmann [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=4DDDF5A9.8060906@kpanic.de \
--to=sassmann@kpanic.de \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=rdunlap@xenotime.net \
--cc=rick@vanrein.org \
--cc=tony.luck@intel.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.