public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@yandex.ru>
To: "zhao, forrest" <forrest.zhao@intel.com>
Cc: Linux MTD <linux-mtd@lists.infradead.org>,
	tglx@linutronix.de, Jarkko Lavinen <jarkko.lavinen@nokia.com>
Subject: Re: JFFS2 CVS broken after 2005/11/14
Date: Wed, 14 Dec 2005 09:42:39 +0300	[thread overview]
Message-ID: <439FBEDF.7000506@yandex.ru> (raw)
In-Reply-To: <1134545396.27194.11.camel@localhost.localdomain>

zhao, forrest wrote:

>Hi, Artem
>
>I would change the mail subject to avoid the confusion.
>
>I did a lot of regression test today.......
>1 I checked in the EBH patch on 2005/11/04, so I checked out
>CVS snapshot of 2005/11/05. It works very well.
>2 I checked in the 1:1 mapping patch on 2005/11/11, so I checked
>out CVS snapshot of 2005/11/12. It works very well.
>3 I checked out CVS snapshot of 2005/11/13. It works very well.
>4 I checked out CVS snapshot of 2005/11/14. There're error 
>messages like the below posted by Jarkko.
>  
>
Actually even without that patch JFFS2 doesn't work. I don't know which 
regression tests you did, but JFFS2 fails to do simle a thing:

mount
copy a file
unmount
mount

and it is reproducable on nandsim.

Artem.

  parent reply	other threads:[~2005-12-14  7:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-11 14:12 EBH question 1 Artem B. Bityutskiy
2005-12-12  6:07 ` zhao, forrest
2005-12-12 10:30   ` Artem B. Bityutskiy
2005-12-13  6:26     ` zhao, forrest
2005-12-13  6:51       ` zhao, forrest
2005-12-13 11:47       ` Jarkko Lavinen
     [not found]         ` <1134545396.27194.11.camel@localhost.localdomain>
2005-12-14  6:42           ` Artem Bityutskiy [this message]
2005-12-14  8:30             ` JFFS2 CVS broken after 2005/11/14 zhao, forrest
2005-12-19 12:01       ` EBH question 1 Artem B. Bityutskiy
2005-12-21  6:49         ` zhao, forrest
2005-12-21  9:16         ` JFFS2 after CVS snapshot 2005/11/13 is broken on nandsim zhao, forrest

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=439FBEDF.7000506@yandex.ru \
    --to=dedekind@yandex.ru \
    --cc=forrest.zhao@intel.com \
    --cc=jarkko.lavinen@nokia.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.de \
    /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