mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: viro@parcelfarce.linux.theplanet.co.uk
To: Linus Torvalds <torvalds@osdl.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Stephen Hemminger <shemminger@osdl.org>,
	jffs-dev@axis.com,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix type mismatch in jffs.
Date: Wed, 10 Sep 2003 20:03:04 +0100	[thread overview]
Message-ID: <20030910190303.GP454@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0309101152060.25211-100000@home.osdl.org>

On Wed, Sep 10, 2003 at 11:54:13AM -0700, Linus Torvalds wrote:
> 
> On Wed, 10 Sep 2003 viro@parcelfarce.linux.theplanet.co.uk wrote:
> > 
> > JFFS is host-endian.  If you want to make it swing both ways - feel free,
> 
> Please don't.
> 
> Dual-endianness is _evil_.
> 
> Admittedly host-endian is stupid too, but it's less stupid than being 
> dual.
> 
> The only sane thing to do is fixed-endianness. I'm sure the m68k people 
> remember being forced to fix their ext2 partitions back in the bad old 
> days. It's painful once, but after that, fixed-endian is a lot more 
> efficient and much simpler to handle.

	a) you've snipped the critical part ;-)
	b) nobody sane uses that beast these days
	c) if somebody wants to grow a private patch - it's their time,
after all...

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...

  reply	other threads:[~2003-09-10 19:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-09 21:44 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 [this message]
2003-09-10 19:16           ` Russell King
2003-09-11 16:50             ` Jörn Engel

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=20030910190303.GP454@parcelfarce.linux.theplanet.co.uk \
    --to=viro@parcelfarce.linux.theplanet.co.uk \
    --cc=geert@linux-m68k.org \
    --cc=jffs-dev@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shemminger@osdl.org \
    --cc=torvalds@osdl.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

Powered by JetHome