All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: monstr@monstr.eu
Cc: microblaze-uclinux@itee.uq.edu.au, linux-kernel@vger.kernel.org,
	linux-arch@vger.kernel.org
Subject: Re: [microblaze-uclinux] Re: [PATCH v2 22/22] bitops: remove minix bitops from asm/bitops.h
Date: Mon, 25 Oct 2010 15:31:35 +0200	[thread overview]
Message-ID: <201010251531.35485.arnd@arndb.de> (raw)
In-Reply-To: <4CC4C1B4.9090907@monstr.eu>

On Monday 25 October 2010, Michal Simek wrote:
> > If upcomming microblade little-endian mode will use little-endian
> > bitmaps for minixfs, microblade can continue to select
> > CONFIG_MINIX_FS_NATIVE_ENDIAN and you don't need to change it.
> > 
> > But if it will use big-endian bitmaps, it may need some extra work
> > to support it. Becuase there is no little-endian architecture
> > which uses bit-endian bitmaps for minixfs.
> 
> As I wrote I don't know anybody who wants to use minixfs that's why we don't
> need to do anything with it. I can test it but it has no high priority.

I think it needs to be set up in a way that new architectures (and those
that never cared about minixfs) automatically get a reasonable default
and should not need to set anything.

I don't see a reason why little-endian microblaze should use big-endian
bitops in minixfs, since that file system layout would also be incompatible
with every other one.

CONFIG_MINIX_FS_NATIVE_ENDIAN seems reasonable for both big- and little-
endian microblaze, but new architectures should just keep the default
little-endian bitops IMHO.
I also don't see a reason for testing. Any new users on microblaze or
future architectures would use a modern file system anyway.

	Arnd

  reply	other threads:[~2010-10-25 13:31 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1287672077-5797-1-git-send-email-akinobu.mita@gmail.com>
2010-10-21 14:40 ` [PATCH v2 01/22] bitops: merge little and big endian definisions in asm-generic/bitops/le.h Akinobu Mita
2010-10-21 15:06   ` Arnd Bergmann
2010-10-21 14:40 ` [PATCH v2 02/22] bitops: rename generic little-endian bitops functions Akinobu Mita
2010-10-21 14:40 ` Akinobu Mita
2010-10-21 14:40   ` Akinobu Mita
2010-10-21 14:40   ` Akinobu Mita
2010-10-21 15:07   ` Arnd Bergmann
2010-10-21 15:07     ` Arnd Bergmann
2010-10-21 15:07     ` Arnd Bergmann
2010-10-21 15:07   ` Arnd Bergmann
2010-10-31 14:02   ` Hans-Christian Egtvedt
2010-10-31 14:02     ` Hans-Christian Egtvedt
2010-10-21 14:40 ` [PATCH v2 03/22] s390: introduce little-endian bitops Akinobu Mita
2010-10-21 15:08   ` Arnd Bergmann
2010-10-21 14:40 ` [PATCH v2 04/22] arm: " Akinobu Mita
2010-10-21 14:40   ` Akinobu Mita
2010-10-21 14:41 ` [PATCH v2 05/22] m68k: " Akinobu Mita
2010-10-21 14:41 ` Akinobu Mita
2010-10-21 14:41   ` Akinobu Mita
2010-10-21 14:41 ` [PATCH v2 06/22] m68knommu: " Akinobu Mita
2010-10-21 14:41   ` Akinobu Mita
2010-10-22  5:47   ` Greg Ungerer
2010-10-22  5:47     ` Greg Ungerer
2010-10-21 14:41 ` Akinobu Mita
2010-10-21 14:41 ` [PATCH v2 07/22] bitops: introduce little-endian bitops for most architectures Akinobu Mita
2010-10-21 14:41 ` [PATCH v2 08/22] rds: stop including asm-generic/bitops/le.h Akinobu Mita
2010-10-21 14:41 ` [PATCH v2 09/22] kvm: " Akinobu Mita
2010-10-21 14:41 ` [PATCH v2 10/22] asm-generic: use little-endian bitops Akinobu Mita
2010-10-21 14:41 ` [PATCH v2 11/22] ext3: " Akinobu Mita
2010-10-21 14:41   ` Akinobu Mita
2010-10-21 14:41   ` Akinobu Mita
2010-10-21 14:41 ` [PATCH v2 12/22] ext4: " Akinobu Mita
2010-10-21 14:41 ` [PATCH v2 13/22] ocfs2: " Akinobu Mita
2010-10-21 14:41   ` [Ocfs2-devel] " Akinobu Mita
2010-10-21 14:41 ` [PATCH v2 14/22] nilfs2: " Akinobu Mita
2010-10-21 14:41 ` [PATCH v2 15/22] reiserfs: " Akinobu Mita
2010-10-21 14:41 ` [PATCH v2 16/22] udf: " Akinobu Mita
2010-10-21 14:41 ` [PATCH v2 17/22] ufs: " Akinobu Mita
2010-10-21 14:41 ` [PATCH v2 18/22] md: use little-endian bit operations Akinobu Mita
2010-10-21 14:41 ` [PATCH v2 19/22] dm: " Akinobu Mita
2010-10-21 14:41 ` [PATCH v2 20/22] bitops: remove ext2 non-atomic bitops from asm/bitops.h Akinobu Mita
2010-10-21 17:52   ` Andreas Dilger
2010-10-22  7:56     ` Akinobu Mita
2010-10-21 14:41 ` [PATCH v2 21/22] m68k: remove inline asm from minix_find_first_zero_bit Akinobu Mita
2010-10-21 14:41 ` Akinobu Mita
2010-10-21 14:41   ` Akinobu Mita
2010-10-21 14:41 ` [PATCH v2 22/22] bitops: remove minix bitops from asm/bitops.h Akinobu Mita
2010-10-21 14:41   ` Akinobu Mita
2010-10-21 14:41   ` Akinobu Mita
2010-10-21 14:41   ` Akinobu Mita
2010-10-21 15:10   ` Arnd Bergmann
2010-10-21 15:10   ` Arnd Bergmann
2010-10-21 15:10     ` Arnd Bergmann
2010-10-21 15:10     ` Arnd Bergmann
2010-10-21 15:10     ` Arnd Bergmann
2010-10-21 23:19   ` Michal Simek
2010-10-21 23:19   ` Michal Simek
2010-10-21 23:19     ` Michal Simek
2010-10-21 23:19     ` Michal Simek
2010-10-22  7:55     ` Akinobu Mita
2010-10-22  7:55       ` Akinobu Mita
2010-10-22  7:55       ` Akinobu Mita
2010-10-22  7:55       ` Akinobu Mita
2010-10-24 23:31       ` [microblaze-uclinux] " Michal Simek
2010-10-25 13:31         ` Arnd Bergmann [this message]
2010-10-22  7:55     ` Akinobu Mita
2010-10-22  5:40   ` Greg Ungerer
2010-10-22  5:40   ` Greg Ungerer
2010-10-22  5:40     ` Greg Ungerer
2010-10-22  5:40     ` Greg Ungerer
2010-10-22  5:40     ` Greg Ungerer
2010-10-21 14:41 ` Akinobu Mita

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=201010251531.35485.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=microblaze-uclinux@itee.uq.edu.au \
    --cc=monstr@monstr.eu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.