From: Artem Bityutskiy <dedekind1@gmail.com>
To: Murali N <nalajala.murali@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Doubt regarding mtd test ( mtd_oobtest ) interpretation of oob data !
Date: Wed, 16 Sep 2009 10:23:39 +0300 [thread overview]
Message-ID: <1253085819.3778.5.camel@localhost> (raw)
In-Reply-To: <630851df0909160009w35efd6b2kb058593b59e1be66@mail.gmail.com>
On Wed, 2009-09-16 at 12:39 +0530, Murali N wrote:
> Hi All,
> i have a doubt on how the OOB data is being managed in MTD driver.
> Recently i have enabled mtd-tests to test my driver for mtd
> compliance.After i ran "mtd_oobtest" i was messed up with test and
> come up with few questions:
>
> 1) Is these tests are well validated? can i trust these tests 100%
> compliant to MTD API specification?
Not necessarily. We wrote these tests to test our OneNAND, and they
may contain bugs.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2009-09-16 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 7:09 Doubt regarding mtd test ( mtd_oobtest ) interpretation of oob data ! Murali N
2009-09-16 7:23 ` Artem Bityutskiy [this message]
2009-09-16 9:36 ` Artem Bityutskiy
2009-09-16 10:20 ` Murali N
2009-09-16 10:50 ` Artem Bityutskiy
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=1253085819.3778.5.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nalajala.murali@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.