From: David Brownell <david-b@pacbell.net>
To: Linux MTD <linux-mtd@lists.infradead.org>
Cc: Kevin Hilman <khilman@deeprootsystems.com>
Subject: Re: [patch 2.6.29-rc3] NAND: fix "raw" reads with ECC syndrome layouts
Date: Thu, 5 Feb 2009 14:34:00 -0800 [thread overview]
Message-ID: <200902051434.00831.david-b@pacbell.net> (raw)
In-Reply-To: <200902021734.12505.david-b@pacbell.net>
On Monday 02 February 2009, David Brownell wrote:
> The current syndrome-based drivers in mainline all seem to use one
> chunk per page; which is presumably why they've not hit this bug.
Hmm, no comments? It seems the ECC_HW_SYNDROME stuff isn't
especially familiar to many folk...
> Fix ... by adding read/write page_raw_syndrome() routines as
> siblings of the existing non-raw routines; "raw" just means to
> bypass the ECC computations, not mutate data and OOB layout.
prev parent reply other threads:[~2009-02-05 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 1:34 [patch 2.6.29-rc3] NAND: fix "raw" reads with ECC syndrome layouts David Brownell
2009-02-05 22:34 ` David Brownell [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=200902051434.00831.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=khilman@deeprootsystems.com \
--cc=linux-mtd@lists.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