From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] NAND: allow custom SW ECC when using nand plat driver
Date: Thu, 20 Dec 2012 17:19:40 -0600 [thread overview]
Message-ID: <1356045580.21086.14@snotra> (raw)
In-Reply-To: <1356015949.52192.YahooMailRC@web185003.mail.gq1.yahoo.com> (from ckiick@att.net on Thu Dec 20 09:05:49 2012)
On 12/20/2012 09:05:49 AM, Chris Kiick wrote:
> Hi,
> Well, you are of course 100% correct. I went back and took out the
> nand plat
> stuff, made my own driver and used NAND_ECC_HW mode. A few tweaks
> and it works
> just great. No changes needed to nand base code.
>
> The mode names are a bit misleading, perhaps someone could document
> them in
> the README?
Patches welcome. :-)
> What do I do to withdraw the patch? Or does it just get bounced out
> of the
> queue.
An e-mail reply is fine (which you just did).
-Scott
prev parent reply other threads:[~2012-12-20 23:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 23:27 [U-Boot] [PATCH] NAND: allow custom SW ECC when using nand plat driver Chris Kiick
2012-12-19 19:02 ` Scott Wood
2012-12-19 21:16 ` Chris Kiick
2012-12-19 21:40 ` Scott Wood
2012-12-19 21:46 ` Scott Wood
2012-12-20 15:05 ` Chris Kiick
2012-12-20 23:19 ` Scott Wood [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=1356045580.21086.14@snotra \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.de \
/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