All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	linux-arch@vger.kernel.org, Vivek Goyal <vgoyal@in.ibm.com>
Subject: Re: Which architectures need 64-bit resources?
Date: Tue, 7 Nov 2006 09:36:41 +0000	[thread overview]
Message-ID: <20061107093641.GA2570@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20061106163243.GN27140@parisc-linux.org>

On Mon, Nov 06, 2006 at 09:32:43AM -0700, Matthew Wilcox wrote:
> On Mon, Nov 06, 2006 at 04:02:06PM +0000, Ralf Baechle wrote:
> > On Mon, Nov 06, 2006 at 05:23:37AM -0700, Matthew Wilcox wrote:
> > 
> > > +       bool "64 bit Memory and IO resources (EXPERIMENTAL)" if (!64BIT && (ARM || X86 || MIPS || PPC) && EXPERIMENTAL)
> > 
> > For MIPS at least it would be needed for a few platforms only, so I'd
> > like to do "select RESOURCES_64BIT" as suitable for a platform. in the
> > big machine selection menu in arch/mips/Kconfig.
> 
> I don't see why you shouldn't do that anyway ... seems like ARM wants to
> do the same thing.  In fact, I'd go so far as to say this isn't an option
> that users should ever be asked.  You can tell by the help text for it:

For the ARM bits...

Acked-by: Russell King <rmk+kernel@arm.linux.org.uk>

Thanks.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

      parent reply	other threads:[~2006-11-07  9:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 12:23 Which architectures need 64-bit resources? Matthew Wilcox
2006-11-06 12:52 ` Arnd Bergmann
2006-11-06 16:02 ` Ralf Baechle
2006-11-06 16:32   ` Matthew Wilcox
2006-11-06 17:13     ` Ralf Baechle
2006-11-07  1:37     ` Geert Uytterhoeven
2006-11-07  3:33       ` Matthew Wilcox
2006-11-07  9:36     ` Russell King [this message]

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=20061107093641.GA2570@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-arch@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=ralf@linux-mips.org \
    --cc=vgoyal@in.ibm.com \
    /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.