From: Mike Dunn <mikedunn@newsguy.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
prabhakar@freescale.com
Subject: Re: [PATCH] mtd: fsl_ifc_nand: fix eccstrength for ecc8
Date: Wed, 29 May 2013 11:14:24 -0700 [thread overview]
Message-ID: <51A64580.2010206@newsguy.com> (raw)
In-Reply-To: <20130528234534.GA22340@home.buserror.net>
On 05/28/2013 04:45 PM, Scott Wood wrote:
> Commit 44df4d11b8f573e9efcba94d63e6a1ad148c76d0 ("mtd: nand: fix
> incorrect ecc strength values") set eccstrength to 4 for IFC, but it is
> 8 in one configuration.
>
> Signed-off-by: Scott Wood <scottwood@freescale.com>
Acked-by: Mike Dunn <mikedunn@newsguy.com>
Missed that... Sorry about that Scott.
Thanks,
Mike
prev parent reply other threads:[~2013-05-29 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 23:45 [PATCH] mtd: fsl_ifc_nand: fix eccstrength for ecc8 Scott Wood
2013-05-29 18:14 ` Mike Dunn [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=51A64580.2010206@newsguy.com \
--to=mikedunn@newsguy.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=prabhakar@freescale.com \
--cc=scottwood@freescale.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 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).