From: Borislav Petkov <bp@alien8.de>
To: Matthew Wilcox <willy@infradead.org>
Cc: Waiman Long <longman@redhat.com>,
Jonathan Corbet <corbet@lwn.net>, Tony Luck <tony.luck@intel.com>,
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: Tue, 5 May 2020 18:03:08 +0200 [thread overview]
Message-ID: <20200505160308.GA25446@zn.tnic> (raw)
In-Reply-To: <20200505154816.GH16070@bombadil.infradead.org>
On Tue, May 05, 2020 at 08:48:16AM -0700, Matthew Wilcox wrote:
> 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".
Yes, that should not talk about 64-bit systems but about the length of
the word the memory controller uses to create the ECC check bits out of.
That whole doc needs checking/fixing.
> The extra 8 bits which are used for error detection and correction
> are referred to as the *syndrome*\ [#f1]_\ [#f2]_.
Well, I know it as "The syndrome field uniquely identifies the failing
bit positions of a correctable ECC error." and depending on the error
severity you can have correctable and uncorrectable syndromes.
I don't think the syndrome is the ECC word but it might be, depending
on the ECC algorithm used or it might be that what I pasted above. That
would need deeper digging.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-05-05 16:03 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 [this message]
2020-05-06 16:21 ` Waiman Long
2020-05-06 16:19 ` Waiman Long
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=20200505160308.GA25446@zn.tnic \
--to=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=longman@redhat.com \
--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