All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: gleixner@autronix.de
Cc: linux-mtd@lists.infradead.org, jffs-dev@axis.com
Subject: Re: JFFS2 & NAND
Date: Sun, 17 Feb 2002 17:25:39 +0000	[thread overview]
Message-ID: <21587.1013966739@redhat.com> (raw)
In-Reply-To: <02021712440204.08654@thomas>

gleixner@autronix.de said:
> Maybe we  could reduce the information to a filesystem type and define
> the oob-layout  as constants in a .h file. That would be less overhead
> but gives the  flexibility for both chip and filesystem driver to use
> free oob layouts. It would be not a big hack to rearrange it that way.

I think that might be best. After all, there are only a limited number of 
such arrangements. 

I'd actually like to overhaul all the oob and ecc stuff in the mtd_info 
structure - I don't like any of it very much. If we can make do with the 
existing API for a while longer, then we can give some serious thought to 
its replacement. 

--
dwmw2

  reply	other threads:[~2002-02-17 17:14 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
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 [this message]
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=21587.1013966739@redhat.com \
    --to=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.