Re: CRAMFS

[H. Peter Anvin]

Followup to:  <35438.128.107.165.13.1068235628.squirrel@xxxxxxxxxxxxxxxx>
By author:    "Bradley Bozarth" <prettygood@xxxxxxxxxxxxxxx>
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@xxxxxxxxxxxxx> at work, <hpa@xxxxxxxxx> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/