From: "Franklin S Cooper Jr." <fcooper@ti.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: <computersforpeace@gmail.com>, <linux-mtd@lists.infradead.org>,
<daniel.thompson@linaro.org>, <xiaolei.li@mediatek.com>,
Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
Subject: Re: [PATCH] mtd: nand: tests: fix regression introduced in mtd_nandectest
Date: Wed, 2 Mar 2016 09:50:19 -0600 [thread overview]
Message-ID: <56D70BBB.1020004@ti.com> (raw)
In-Reply-To: <20160301221755.093f5223@bbrezillon>
On 03/01/2016 03:17 PM, Boris Brezillon wrote:
> Hi Jorge,
>
> On Tue, 1 Mar 2016 16:04:00 -0500
> Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org> wrote:
>
>> Offending Commit: 6e94119 "mtd: nand: return consistent error codes in
>> ecc.correct() implementations"
>>
>> The new error code was not being handled properly in double bit error
>> detection.
>>
>> Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
> Reviewed-by: Boris Brezillon <boris.brezillon@free-electrons.com>
>
> Thanks,
>
> Boris
We just encountered this problem and this patch fixed it.
Tested-by: Franklin S Cooper Jr <fcooper@ti.com>
>> ---
>> drivers/mtd/tests/mtd_nandecctest.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/mtd/tests/mtd_nandecctest.c b/drivers/mtd/tests/mtd_nandecctest.c
>> index 7931615..88b6c81 100644
>> --- a/drivers/mtd/tests/mtd_nandecctest.c
>> +++ b/drivers/mtd/tests/mtd_nandecctest.c
>> @@ -187,7 +187,7 @@ static int double_bit_error_detect(void *error_data, void *error_ecc,
>> __nand_calculate_ecc(error_data, size, calc_ecc);
>> ret = __nand_correct_data(error_data, error_ecc, calc_ecc, size);
>>
>> - return (ret == -1) ? 0 : -EINVAL;
>> + return (ret == -EBADMSG) ? 0 : -EINVAL;
>> }
>>
>> static const struct nand_ecc_test nand_ecc_test[] = {
>
>
next prev parent reply other threads:[~2016-03-02 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 21:04 [PATCH] mtd: nand: tests: fix regression introduced in mtd_nandectest Jorge Ramirez-Ortiz
2016-03-01 21:17 ` Boris Brezillon
2016-03-02 15:50 ` Franklin S Cooper Jr. [this message]
2016-03-05 1:02 ` Brian Norris
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=56D70BBB.1020004@ti.com \
--to=fcooper@ti.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=daniel.thompson@linaro.org \
--cc=jorge.ramirez-ortiz@linaro.org \
--cc=linux-mtd@lists.infradead.org \
--cc=xiaolei.li@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.