From: Scott Wood <scottwood@freescale.com>
To: <MichaelHench@gmail.com>
Cc: linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org,
mlcreech@gmail.com, mhench@elutions.com
Subject: Re: [PATCH v2] mtd: eLBC NAND: update ecc_stats.corrected when lteccr available
Date: Tue, 26 Jul 2011 14:05:54 -0500 [thread overview]
Message-ID: <20110726140554.2096b12d@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <CAHyXW604AxBGO=AEAyOcba2VfsjVve+RV7_A8QXaUpJRfAsq3Q@mail.gmail.com>
On Tue, 26 Jul 2011 13:59:25 -0500
Michael Hench <michaelhench@gmail.com> wrote:
> update ecc_stats.corrected if LTECCR register is available.
>
> v2: kernel standard C formatting
Missed a couple:
> + if(lteccr & 0x000F000F)
> + out_be32(&lbc->lteccr, 0x000F000F); /* clear lteccr */
> + if(lteccr & 0x000F0000)
> + mtd->ecc_stats.corrected++;
-Scott
prev parent reply other threads:[~2011-07-26 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 18:59 [PATCH v2] mtd: eLBC NAND: update ecc_stats.corrected when lteccr available Michael Hench
2011-07-26 19:05 ` 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=20110726140554.2096b12d@schlenkerla.am.freescale.net \
--to=scottwood@freescale.com \
--cc=MichaelHench@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mhench@elutions.com \
--cc=mlcreech@gmail.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).