linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Drebes <lists-receive@programmierforen.de>
To: Phillip Lougher <phillip@lougher.demon.co.uk>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/2] cramfs: Add mount option "swapendian"
Date: Fri, 16 Nov 2007 11:28:08 +0100	[thread overview]
Message-ID: <200711161128.08944.lists-receive@programmierforen.de> (raw)
In-Reply-To: <473CCCAC.5010304@lougher.demon.co.uk>

Am Donnerstag, 15. November 2007 23:48 schrieb Phillip Lougher:
> > So a "v2" cramfs would be a great idea.
> 
> That is what I always considered Squashfs to be.  But I also made the 
> mistake of making Squashfs both little and big endian.  That's going to
> be fixed and then I'll make a second attempt at submitting it for
> inclusion in the mainline kernel.
I didn't have a closer look on squashfs, but I am going to have it this weekend.
So far, it seems as if no "cramfs v2" is needed. My proposal is the following:

I'll write a new patch for inclusion in the mainline kernel that makes cramfs
"little endian only". For people who really want to be able to mount filesystems
with both kinds of endianness there will be a seperate patch (not intended to be
merged into mainline) available somewhere on the net (my website or so). It will
definitely be marked as non-official in order to prevent people from creating
images in big endian. Officially, cramfs should only support little endian images.
If squashfs will be merged, cramfs should be marked as obsolete.

	Andi

  reply	other threads:[~2007-11-16 10:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 20:29 [PATCH 0/2] cramfs: support for other endianness Andi Drebes
2007-11-15 20:35 ` [PATCH 0/2] cramfs: Add mount option "swapendian" Andi Drebes
2007-11-15 20:45   ` Linus Torvalds
2007-11-15 20:46     ` Linus Torvalds
2007-11-15 20:51       ` Christoph Hellwig
2007-11-15 20:49     ` Christoph Hellwig
2007-11-15 20:57       ` Linus Torvalds
2007-11-15 21:15     ` Andi Drebes
2007-11-15 21:37       ` Linus Torvalds
2007-11-15 22:48         ` Phillip Lougher
2007-11-16 10:28           ` Andi Drebes [this message]
2007-11-16 15:44             ` Linus Torvalds
2007-11-15 21:03   ` Jörn Engel
2007-11-15 20:37 ` [PATCH 0/2] cramfs: update README file Andi Drebes
2007-11-15 20:43 ` [PATCH 0/2] cramfs: support for other endianness Andi Drebes

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=200711161128.08944.lists-receive@programmierforen.de \
    --to=lists-receive@programmierforen.de \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=phillip@lougher.demon.co.uk \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).