From: Brian Norris <computersforpeace@gmail.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: "Huang Shijie" <b32955@freescale.com>,
linux-mtd@lists.infradead.org,
"Ezequiel Garcia" <ezequiel@vanguardiasur.com.ar>,
"Guido Martínez" <guido@vanguardiasur.com.ar>,
"Pekon Gupta" <pekon@ti.com>
Subject: Re: [PATCH v2] nandtest: Introduce multiple reads & check iterations
Date: Fri, 30 May 2014 17:01:44 -0700 [thread overview]
Message-ID: <20140531000144.GB9970@ld-irv-0074> (raw)
In-Reply-To: <1401194435.1304.143.camel@sauron.fi.intel.com>
On Tue, May 27, 2014 at 03:40:35PM +0300, Artem Bityutskiy wrote:
> 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.
Thanks for the hint :)
Looks good to me. Pushed to mtd-utils.git. Thanks!
Brian
prev parent reply other threads:[~2014-05-31 0:02 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
2014-05-31 0:01 ` Brian Norris [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=20140531000144.GB9970@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=b32955@freescale.com \
--cc=dedekind1@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