From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: "Huang Shijie" <b32955@freescale.com>,
"Brian Norris" <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org, "Pekon Gupta" <pekon@ti.com>,
"Guido Martínez" <guido@vanguardiasur.com.ar>
Subject: Re: [PATCH v2] nandtest: Introduce multiple reads & check iterations
Date: Tue, 27 May 2014 15:40:35 +0300 [thread overview]
Message-ID: <1401194435.1304.143.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1399388869-5815-2-git-send-email-ezequiel@vanguardiasur.com.ar>
On Tue, 2014-05-06 at 12:07 -0300, Ezequiel Garcia wrote:
> The current nandtest performs a simple test which consists of:
>
> 1. erase block
> 2. write data
> 3. read and verify
>
> In order to improve the nandtest strength, this commit adds a new parameter
> to increase the number of "read and verify" iterations. In other words,
> the test now consists of:
>
> 1. erase block
> 2. write data
> 3. read and verify (N times)
I think this is reasonable, but there were some skeptic replies, so
probably another approver's voice would not hurt. Let me give you my
Acked-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
and drop Brian a hint that if he things the same way, he could just push
this driver, or approve and then I can push.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2014-05-27 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 15:07 [PATCH v2] nandtest: Allow multiple read & check iterations Ezequiel Garcia
2014-05-06 15:07 ` [PATCH v2] nandtest: Introduce multiple reads " Ezequiel Garcia
2014-05-27 12:40 ` Artem Bityutskiy [this message]
2014-05-31 0:01 ` 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=1401194435.1304.143.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=b32955@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=guido@vanguardiasur.com.ar \
--cc=linux-mtd@lists.infradead.org \
--cc=pekon@ti.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).