All of lore.kernel.org
 help / color / mirror / Atom feed
From: p2@mind.be (Peter De Schrijver)
To: Thomas Gleixner <gleixner@autronix.de>
Cc: David Woodhouse <dwmw2@infradead.org>,
	linux-mtd@lists.infradead.org, jffs-dev@axis.com
Subject: Re: JFFS2 & NAND
Date: Thu, 14 Feb 2002 18:22:40 +0100	[thread overview]
Message-ID: <20020214172240.GA16142@mind.be> (raw)
In-Reply-To: <02021416570005.29375@thomas>

Hi,

On Thu, Feb 14, 2002 at 04:57:00PM +0100, Thomas Gleixner wrote:
> Since the discussion is broken and I'm answering my question to myself for a 
> few days, I ask me, if the interest on this problem is gone.
> 

No, certainly not. Unfortunately I don't have any hardware available now
to test on. As soon as I have, I will certainly test JFFS2 on NAND and
help fixing bugs.

> I have spent a lot of time to make this running. It does, except one 
> unresolved issue, when we fail in flush_wbuf and wbuf contains more than the 
> actual node.
> I'm willing to solve this too, but as I mentioned before, my knowlegde of 
> JFFS2 is not deep enough yet. Is there anybody, who want's to implement this 
> basicly or give me at least some pointers how to do it.
> 

Peter.

  reply	other threads:[~2002-02-14 17:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-14 15:57 JFFS2 & NAND Thomas Gleixner
2002-02-14 17:22 ` Peter De Schrijver [this message]
2002-02-14 17:27 ` David Woodhouse
2002-02-14 17:43   ` Thomas Gleixner
2002-02-17  9:51     ` David Woodhouse
2002-02-17 11:44       ` Thomas Gleixner
2002-02-17 17:25         ` David Woodhouse
2002-02-17 19:36           ` Thomas Gleixner
2002-02-18  8:48             ` Thomas Gleixner
2002-02-18  8:46               ` David Woodhouse
2002-02-18  9:26                 ` Thomas Gleixner
2002-02-18  9:29                   ` David Woodhouse
2002-02-18  9:48                     ` Thomas Gleixner
2002-02-18 16:02                       ` Thomas Gleixner

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=20020214172240.GA16142@mind.be \
    --to=p2@mind.be \
    --cc=dwmw2@infradead.org \
    --cc=gleixner@autronix.de \
    --cc=jffs-dev@axis.com \
    --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 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.