From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: viro@parcelfarce.linux.theplanet.co.uk,
Linus Torvalds <torvalds@osdl.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Stephen Hemminger <shemminger@osdl.org>,
jffs-dev@axis.com,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] fix type mismatch in jffs.
Date: Thu, 11 Sep 2003 18:50:59 +0200 [thread overview]
Message-ID: <20030911165059.GC3989@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20030910201607.G30046@flint.arm.linux.org.uk>
On Wed, 10 September 2003 20:16:07 +0100, Russell King wrote:
> On Wed, Sep 10, 2003 at 08:03:04PM +0100, viro@parcelfarce.linux.theplanet.co.uk wrote:
> >
> > Seriously, though, by now fs/jffs/* has only one real use - extracting
> > data from old filesystem. IIRC, there was even a talk about having it go
> > the way of ext and xiafs. He's dead, Jim...
>
> It isn't that dead - I get the occasional patch from people wanting to keep
> it working, although I really wish people would send them to dwmw2 rather
> than myself.
Yes, it still beats jffs2 in cases where people have <=5 flash blocks
and want a r/w filesystem on them. Until David, myself or someone
else finds the time to improve jffs2 for corner cases like this, jffs
has a use - sadly.
Jörn
--
When you close your hand, you own nothing. When you open it up, you
own the whole world.
-- Li Mu Bai in Tiger & Dragon
prev parent reply other threads:[~2003-09-11 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 21:44 [PATCH] fix type mismatch in jffs Stephen Hemminger
2003-09-10 2:40 ` viro
2003-09-10 17:14 ` Geert Uytterhoeven
2003-09-10 18:18 ` viro
2003-09-10 18:54 ` Linus Torvalds
2003-09-10 19:03 ` viro
2003-09-10 19:16 ` Russell King
2003-09-11 16:50 ` Jörn Engel [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=20030911165059.GC3989@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=dwmw2@infradead.org \
--cc=geert@linux-m68k.org \
--cc=jffs-dev@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=torvalds@osdl.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).