From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
vimal singh <vimal.newwork@gmail.com>
Subject: Re: [PATCH 3/3 -v3] MTD: Add nand_ecc test module
Date: Thu, 22 Oct 2009 08:13:38 +0300 [thread overview]
Message-ID: <1256188418.29856.429.camel@localhost> (raw)
In-Reply-To: <20091022032415.GA3637@localhost.localdomain>
On Thu, 2009-10-22 at 05:24 +0200, ext Akinobu Mita wrote:
> On Wed, Oct 21, 2009 at 11:51:35AM +0300, Artem Bityutskiy wrote:
> > On Wed, 2009-10-21 at 17:34 +0900, Akinobu Mita wrote:
> > > This module tests NAND ECC functions.
> > >
> > > The test is simple.
> > >
> > > 1. Create a 256 or 512 bytes block of data filled with random bytes (data)
> > > 2. Duplicate the data block and inject single bit error (error_data)
> > > 3. Try to correct error_data
> > > 4. Compare data and error_data
> > >
> > > Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
> > > Cc: David Woodhouse <dwmw2@infradead.org>
> > > Cc: linux-mtd@lists.infradead.org
> > > Cc: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
> > > Cc: vimal singh <vimal.newwork@gmail.com>
> > > ---
> > > drivers/mtd/tests/Makefile | 1 +
> > > drivers/mtd/tests/nand_ecc-test.c | 87 +++++++++++++++++++++++++++++++++++++
> > > 2 files changed, 88 insertions(+), 0 deletions(-)
> > > create mode 100644 drivers/mtd/tests/nand_ecc-test.c
> >
> > How about a consistent name for the test? All current tests have 'mtd_'
> > prefix. How about make the file to be 'mtd_ecctest.c' ?
>
> OK. I'll rename to mtd_nandecctest.c as vimal said.
>
> > Also, since you anyway need to use these "#defines", I think there is
> > not need to use this splitting. I apologize for leading you that way at
> > the beginning.
>
> Does it mean we don't need MTD_NAND_TESTS and the new mtd_nandecctest
> should exist in MTD_TESTS with that #ifdef checks as I originally did?
Right. The idea was to avoid the ifdefs by cheap price, but now it seems
that was bad idea.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2009-10-22 5:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 8:34 [PATCH 3/3 -v3] MTD: Add nand_ecc test module Akinobu Mita
2009-10-21 8:51 ` Artem Bityutskiy
2009-10-21 9:06 ` vimal singh
2009-10-21 9:43 ` Artem Bityutskiy
2009-10-22 3:24 ` Akinobu Mita
2009-10-22 5:13 ` Artem Bityutskiy [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=1256188418.29856.429.camel@localhost \
--to=artem.bityutskiy@nokia.com \
--cc=akinobu.mita@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=vimal.newwork@gmail.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.