linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@mcmartin.ca>
To: linux-arch@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] Only show RESOURCES_64BIT on relevant architectures
Date: Sun, 28 Oct 2007 16:15:49 -0400	[thread overview]
Message-ID: <20071028201549.GA23138@fattire.cabal.ca> (raw)

To quote lolcats: CONFIG_RESOURCES_64BIT DO NOT WANT!

I *think* I have the logic of this right... Anyway, I was annoyed by
having to do the bloody ugly casts to unsigned long long in
arch-specific code. As near as I can tell, we only want this selectable
in the case of PAE on x86, and some random PPC and MIPS embedded boards.

For everyone else, it should be whatever the value of 64BIT is.

And I can be happy and continue using unsigned long and going about my
merry business.

Signed-off-by: Kyle McMartin <kyle@mcmartin.ca>
---
diff --git a/mm/Kconfig b/mm/Kconfig
index c070ec0..c25a838 100644
--- a/mm/Kconfig
+++ b/mm/Kconfig
@@ -172,6 +172,7 @@ config MIGRATION
 
 config RESOURCES_64BIT
 	bool "64 bit Memory and IO resources (EXPERIMENTAL)" if (!64BIT && EXPERIMENTAL)
+	depends on (MIPS || PPC32 || X86_PAE) || 64BIT
 	default 64BIT
 	help
 	  This option allows memory and IO resources to be 64 bit.

             reply	other threads:[~2007-10-28 20:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-28 20:15 Kyle McMartin [this message]
2007-10-29  1:09 ` [PATCH] Only show RESOURCES_64BIT on relevant architectures David Miller
2007-10-29 15:11   ` Kyle McMartin
2007-10-29  8:10 ` Russell King
2007-10-29 15:21   ` Kyle McMartin
2007-10-29 15:50     ` Russell King
2007-10-30  2:48 ` Ralf Baechle
2007-10-30  3:03   ` Kumar Gala
2007-10-30  8:37     ` Matthew Wilcox
2007-10-30 11:42       ` Ralf Baechle
2007-10-30 12:13         ` Matthew Wilcox
2007-10-30 14:14           ` Ralf Baechle
2007-10-30 20:00           ` Russell King
2007-10-30 14:19       ` Kumar Gala

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=20071028201549.GA23138@fattire.cabal.ca \
    --to=kyle@mcmartin.ca \
    --cc=linux-arch@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).