On Fri, Oct 15, 2010 at 12:53, Arnd Bergmann <arnd@xxxxxxxx> wrote:
On Friday 15 October 2010, Akinobu Mita wrote:
minix bit operations are only used by minix filesystem and useless
by other modules.
Right.
This provides new config option CONFIG_MINIX_FS_LITTLE_ENDIAN and
CONFIG_MINIX_FS_NATIVE_ENDIAN that each architecture selects one of which.
Then we can remove minix bit operations from asm/bitops.h from all
architectures by making them minix filesystem local macros.
I would say that any architecture that defines minix bitops as
little-endian is broken and we should not even need the #define.
You have defined these as "native endian":
always LE:
   Âalpha, blackfin, ia64, score, tile, x86
always BE:
   Âh8300, microblaze, s390, sparc
configurable:
   Âm32r, mips, sh, xtensa
The only ones among these that possibly ever cared about mounting minix
file systems on a big-endian kernel are really old sparc and mips systems,
everyone else probably never noticed their mistake.
I'd say let's define the minix bitops as always LE and be done with it.
Funny, m68k uses the little endian minix file system?
Perhaps this was due to minix using the ext2 accessors? And ext2 being
switched from big to little endian ext2 on m68k, without anyone
noticing the impact
on minix?
Gr{oetje,eeting}s,
            Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
             Â Â -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
