From: Artem Bityutskiy <dedekind1@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: linux-kernel@vger.kernel.org, Heinz.Egger@linutronix.de,
linux-mtd@lists.infradead.org, tim.bird@am.sony.com,
tglx@linutronix.de, Shmulik Ladkani <shmulik.ladkani@gmail.com>
Subject: Re: [RFC v7] UBI: Fastmap support (aka checkpointing)
Date: Sat, 26 May 2012 17:15:44 +0300 [thread overview]
Message-ID: <1338041744.2525.46.camel@koala> (raw)
In-Reply-To: <4FC0E257.1030403@nod.at>
[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]
On Sat, 2012-05-26 at 16:01 +0200, Richard Weinberger wrote:
> > We can start with the UBI tests from the mtd-utils plust the integck
> > test. And whatever goes to my branch should never break them. Do these
> > tests pass now? If not, let's make them pass.
> >
>
> What is "integck" test?
It is a quite extensive FS check which we use for UBIFS. As UBIFS is the
main UBI client - it makes sense to run it. It lives in the
mtd-utils.git/tests/fs/integck
./integck -n8 /mnt/ubifs
would run in. /mnt/ubifs is the ubifs mount-point. -n8 means repeat 8
times.
> UBI tests from mtd-utils pass now.
> The io_paral triggered a race condition on my very fast qemu-kvm test system.
> On my test board with real NAND flash this race never happened.
> Anyway, it's fixed now.
Cool!
> I'm mostly testing with custom scripts, shall I send a patch against UBI tests?
Yes, it would be great to integrate this, of course. I might also want
to send you a patch, then I'd run it.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-26 14:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 11:06 [RFC v7] UBI: Fastmap support (aka checkpointing) Richard Weinberger
2012-05-23 11:06 ` [PATCH] [RFC] UBI: Implement Fastmap support Richard Weinberger
2012-05-26 13:22 ` Artem Bityutskiy
2012-05-31 10:37 ` Adrian Hunter
2012-05-31 13:31 ` Richard Weinberger
2012-06-01 5:47 ` Adrian Hunter
2012-06-01 8:00 ` Richard Weinberger
2012-06-01 8:10 ` Artem Bityutskiy
2012-06-01 8:10 ` Richard Weinberger
2012-06-01 8:47 ` Adrian Hunter
2012-05-26 12:41 ` [RFC v7] UBI: Fastmap support (aka checkpointing) Artem Bityutskiy
2012-05-26 14:01 ` Richard Weinberger
2012-05-26 14:15 ` Artem Bityutskiy [this message]
2012-05-28 6:36 ` Shmulik Ladkani
2012-05-28 6:46 ` Artem Bityutskiy
2012-05-28 9:49 ` Richard Weinberger
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=1338041744.2525.46.camel@koala \
--to=dedekind1@gmail.com \
--cc=Heinz.Egger@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=shmulik.ladkani@gmail.com \
--cc=tglx@linutronix.de \
--cc=tim.bird@am.sony.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).