From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: CRAMFS
Date: 9 Nov 2003 07:15:03 -0800 [thread overview]
Message-ID: <bollln$uu2$1@cesium.transmeta.com> (raw)
In-Reply-To: 35438.128.107.165.13.1068235628.squirrel@mail.yumbrad.com
Followup to: <35438.128.107.165.13.1068235628.squirrel@mail.yumbrad.com>
By author: "Bradley Bozarth" <prettygood@cs.stanford.edu>
In newsgroup: linux.dev.kernel
>
> Daniel Quinlan originally maintained this, now it is orphaned. His endian
> patch, which implemented the correct behavior according to the docs (which
> basically listed always do little endian as a todo), was dropped.
>
> We have been maintaining this patch on our kernel, but it really should go
> in - I don't want to spend a ton of time like I did last time to have it
> dropped again, however - is anyone thinking of maintaining cramfs? What
> are the chances of the endian fix going in if I submit it again? (if even
> the former maintainer had no success). I would maintain cramfs if desired
> - it hasn't really changed in a long time except in regards to higher
> level fs changes.
>
I think Al Viro has been doing a rewrite. You may want to check with him.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
If you send me mail in HTML format I will assume it's spam.
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-11-09 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 20:07 CRAMFS Bradley Bozarth
2003-11-09 15:15 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-09 4:24 cramfs Trever L. Adams
2001-07-16 6:23 ` cramfs Daniel Quinlan
2001-03-23 19:37 RAMFS, CRAMFS and JFFS2(was Re: /linuxrc query) David Woodhouse
2001-03-23 20:25 ` CRAMFS Bjorn Wesen
2001-03-23 22:01 ` CRAMFS Amit D Chaudhary
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='bollln$uu2$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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