public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Peter Grayson <pgrayson@realmsys.com>
To: dedekind@infradead.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: Latest jffs2 broken?
Date: Tue, 06 Sep 2005 03:52:56 -0600	[thread overview]
Message-ID: <1126000376.7119.5.camel@localhost.localdomain> (raw)
In-Reply-To: <1125997245.8135.16.camel@sauron.oktetlabs.ru>

On Tue, 2005-09-06 at 13:00 +0400, Artem B. Bityuckiy wrote:
> I have had my vacation, I will glance what is going on.

Actually, I have just found that an error in the nand driver I am using
is the cause of this problem. The problem only happens with the latest
jffs2 code, but I now know it is not the jffs2 code. In fact, I am now
seeing the performance benefits of the new frag tree stuff and I am
really impressed. Good job!

Pete

      reply	other threads:[~2005-09-06  9:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-23 23:36 Latest jffs2 broken? Peter Grayson
2005-08-26 12:24 ` Ferenc Havasi
2005-08-26 20:01   ` Peter Grayson
2005-09-01  5:02   ` Peter Grayson
2005-09-06  9:00     ` Artem B. Bityuckiy
2005-09-06  9:52       ` Peter Grayson [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=1126000376.7119.5.camel@localhost.localdomain \
    --to=pgrayson@realmsys.com \
    --cc=dedekind@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    /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