From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Bo Shen <voice.shen@atmel.com>
Cc: Josh Wu <josh.wu@atmel.com>,
computersforpeace@gmail.com, linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mtd: atmel_nand: make ecc parameters same as definition
Date: Thu, 12 Jun 2014 09:26:40 +0200 [thread overview]
Message-ID: <53995630.6040902@atmel.com> (raw)
In-Reply-To: <539954CD.5080309@atmel.com>
On 12/06/2014 09:20, Josh Wu :
> Hi, Bo
>
> On 6/11/2014 11:24 AM, Bo Shen wrote:
>> Hi Josh,
>>
>> On 06/09/2014 06:30 PM, Josh Wu wrote:
>>> Hi, Bo
>>>
>>> Thanks for the patch.
>>>
>>> On 6/6/2014 4:02 PM, Bo Shen wrote:
>>>> If the ecc parameter is not the same as definition, when the
>>>> mtd core check these parameters, it will give the unexpected
>>>> result.
>>> Could you be more specific to tell what kind of result will happened?
>>
>> For example:
>> When try to calculate how many bits can correct in one page according
>> to the definition, it will give the wrong result.
>>
>> one page correct bits = (mtd->writesize * ecc->strength) / ecc->size;
>>
>> take the following use case as an example:
>> mtd->writesize = 2048 bytes,
>> ecc->strength = 4 bytes, (for 512 bytes)
>>
>> before this patch, the ecc->size = 2048, so the result is 4 bytes.
>>
>> after this patch, the ecc->size = 512, so the result is 16 bytes.
>>
>> The maximum correct bytes is 16 bytes while not 4 bytes. So, if not align
>
> That is clear enough, thanks. The patch is fine to me. so
> Acked-by: Josh Wu <josh.wu@atmel.com>
So I advice to add this additional information to the commit message:
Can you send a v2 with enhanced commit message.
Thanks, bye,
--
Nicolas Ferre
next prev parent reply other threads:[~2014-06-12 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 8:02 [PATCH] mtd: atmel_nand: make ecc parameters same as definition Bo Shen
2014-06-09 10:30 ` Josh Wu
2014-06-11 3:24 ` Bo Shen
2014-06-12 7:20 ` Josh Wu
2014-06-12 7:26 ` Nicolas Ferre [this message]
2014-06-12 7:45 ` Bo Shen
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=53995630.6040902@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=computersforpeace@gmail.com \
--cc=josh.wu@atmel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=voice.shen@atmel.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).