From: Thomas Gleixner <tglx@linutronix.de>
To: Nick Bane <nick@cecomputing.co.uk>
Cc: "Balloon@Balloonboard.Org" <balloon@balloonboard.org>,
yaffs list <yaffs@toby-churchill.org>,
"Linux-Mtd@Lists.Infradead.Org" <linux-mtd@lists.infradead.org>
Subject: Re: yaffs update#2
Date: Fri, 03 Sep 2004 10:38:40 +0200 [thread overview]
Message-ID: <1094200720.3681.3.camel@lap02.tec.linutronix.de> (raw)
In-Reply-To: <IDEJKGNLJIGGPDGEHFGBKEADEBAA.nick@cecomputing.co.uk>
On Thu, 2004-09-02 at 19:56, Nick Bane wrote:
> Hi folks,
> There are moves afoot to submit yaffs to mainstream linux.
> All opinions about suitability/maturity welcome. The kernel
> mtd layer and yaffs_mtdif have now harmonised so now seems
> a good moment.
Can we look into use the automatic placement of OOB data. Then it would
be using the same mechanisms as JFFS2 and it would be easy to use YAFFS
on DOC and other devices which cannot use the fixed OOB layout scheme ?
tglx
prev parent reply other threads:[~2004-09-03 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 17:56 yaffs update#2 Nick Bane
2004-09-03 8:38 ` Thomas Gleixner [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=1094200720.3681.3.camel@lap02.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=balloon@balloonboard.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nick@cecomputing.co.uk \
--cc=yaffs@toby-churchill.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