From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Pekon Gupta <pekon@ti.com>
Cc: Stefan Roese <sr@denx.de>,
Brian Norris <computersforpeace@gmail.com>,
linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] mtd: nand: omap: ecc.correct: omap_elm_correct_data: return number of bit-flips detected in erased-page
Date: Thu, 20 Mar 2014 11:55:30 -0300 [thread overview]
Message-ID: <20140320145530.GA23161@arch.cereza> (raw)
In-Reply-To: <1395321598-4565-1-git-send-email-pekon@ti.com>
Pekon,
I'm not sure we need such a detailed subject. Just "mtd: nand: omap:
Return detected bitflip count" should be enough.
This goes for your other patches. It's just a nitpick, of course,
but it's good to have commit log consistency.
On Mar 20, Pekon Gupta wrote:
> fixes: commit 62116e5171e00f85a8d53f76e45b84423c89ff34
> mtd: nand: omap2: Support for hardware BCH error correction.
>
Remove these extra whitespace.
> In current omap_elm_correct_data(), an erased-page is also identified based on
> 'bitflip_count <= ecc.strength' per ecc-step (data+oob)
And this extra tab.
> But bitflip_count is ignored, unless errors are detected in other ecc.steps.
> ------------------
> if (bitflip_count) {
> /*
> * number of 0-bits within ECC limits
> * So this may be an erased-page
> */
> stat += bitflip_count;
> }
> [...]
> /* Check if any error reported */
> if (!is_error_reported)
> return 0;
> ------------------
>
We don't need a piece of code here, we can see that in the patch itself.
The commit log should be a text explaining what you are doing, why you are doing
it and perhaps the impact it has.
I suggest that you clean-up this a bit and resend it.
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
prev parent reply other threads:[~2014-03-20 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 13:19 [PATCH] mtd: nand: omap: ecc.correct: omap_elm_correct_data: return number of bit-flips detected in erased-page Pekon Gupta
2014-03-20 14:55 ` Ezequiel Garcia [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=20140320145530.GA23161@arch.cereza \
--to=ezequiel.garcia@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=pekon@ti.com \
--cc=sr@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