From: Waiman Long <longman@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>, Tony Luck <tony.luck@intel.com>,
Borislav Petkov <bp@alien8.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
James Morse <james.morse@arm.com>,
Robert Richter <rrichter@marvell.com>,
linux-edac@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc: Fix some typo errors in ras.rst
Date: Wed, 6 May 2020 12:19:33 -0400 [thread overview]
Message-ID: <eae29941-683c-4501-d3f0-8c33532e8975@redhat.com> (raw)
In-Reply-To: <20200505154816.GH16070@bombadil.infradead.org>
On 5/5/20 11:48 AM, Matthew Wilcox wrote:
> On Tue, May 05, 2020 at 11:10:49AM -0400, Waiman Long wrote:
>> Fix typo errors.
> By reformatting it, you've successfully obscured what typos you've fixed.
> As a result I read the whole paragraph, and ...
>
>> ECC memory
>> ----------
>>
>> -As mentioned on the previous section, ECC memory has extra bits to be
>> -used for error correction. So, on 64 bit systems, a memory module
>> -has 64 bits of *data width*, and 74 bits of *total width*. So, there are
>> -8 bits extra bits to be used for the error detection and correction
>> +As mentioned on the previous section, ECC memory has extra bits to
> s/on/in/
>
>> +be used for error correction. So, on 64 bit systems, a memory module
>> +has 64 bits of *data width*, and 72 bits of *total width*.
> Usually a 64-bit system refers to the width of a pointer. Here, it's
> referring to the width of the memory system, which is rather confusing.
> How about "In the above example" instead of "So, on 64 bit systems".
>
>> So, there
>> +are 8 extra bits to be used for the error detection and correction
>> mechanisms. Those extra bits are called *syndrome*\ [#f1]_\ [#f2]_.
> This would read better as:
>
> The extra 8 bits which are used for error detection and correction
> are referred to as the *syndrome*\ [#f1]_\ [#f2]_.
>
Thanks for the suggestion. Will incorporate that in v2.
-Longman
prev parent reply other threads:[~2020-05-06 16:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 15:10 [PATCH] doc: Fix some typo errors in ras.rst Waiman Long
2020-05-05 15:32 ` Jonathan Corbet
2020-05-05 15:50 ` Waiman Long
2020-05-05 15:48 ` Matthew Wilcox
2020-05-05 16:03 ` Borislav Petkov
2020-05-06 16:21 ` Waiman Long
2020-05-06 16:19 ` Waiman Long [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=eae29941-683c-4501-d3f0-8c33532e8975@redhat.com \
--to=longman@redhat.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=james.morse@arm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rrichter@marvell.com \
--cc=tony.luck@intel.com \
--cc=willy@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).