From: Matthew Wilcox <matthew@wil.cx>
To: linux-arch@vger.kernel.org
Subject: Which architectures need 64-bit resources?
Date: Mon, 6 Nov 2006 05:23:37 -0700 [thread overview]
Message-ID: <20061106122337.GK27140@parisc-linux.org> (raw)
I have a patch sitting in the parisc tree which does:
config RESOURCES_64BIT
- bool "64 bit Memory and IO resources (EXPERIMENTAL)" if (!64BIT && EXPER
IMENTAL)
+ bool "64 bit Memory and IO resources (EXPERIMENTAL)" if (!64BIT && !PARI
SC && EXPERIMENTAL)
default 64BIT
This is a bit selfish really, and it'll lead to something pretty ugly and
unmaintainable ...
+ bool "64 bit Memory and IO resources (EXPERIMENTAL)" if (!64BIT && !PARISC && !M68K && !AVR && !CRIS && !FRV && !H8300 && !M32R && !S390 && !SUPERH && !SPARC && !V850 && !XTENSA && EXPERIMENTAL)
at least if my understanding of those arches needs is correct. Much better
to have the dependencies be positive:
+ bool "64 bit Memory and IO resources (EXPERIMENTAL)" if (!64BIT && (ARM || X86 || MIPS || PPC) && EXPERIMENTAL)
Do I have that set of architectures right? Any others that need 64 bit
resource types? Any there that shouldn't be there? Should we ditch
the EXPERIMENTAL tag at the same time?
next reply other threads:[~2006-11-06 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 12:23 Matthew Wilcox [this message]
2006-11-06 12:52 ` Which architectures need 64-bit resources? 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
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=20061106122337.GK27140@parisc-linux.org \
--to=matthew@wil.cx \
--cc=linux-arch@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