From: Milton Miller <miltonm@bga.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@digeo.com>
Subject: [PATCH] Allow LBD on architectures that support it
Date: Fri, 11 Jul 2003 21:24:23 -0500 (CDT) [thread overview]
Message-ID: <200307120224.h6C2ONNR016854@sullivan.realtime.net> (raw)
While researching the as-iosched division last night (sorry, I slept
and went to work before sending out the patch), I noticed CONFIG_LBD
wasn't in my config file. The following architectures appear to have
the necessary asm/types.h changes:
include/asm-i386/types.h:typedef u64 sector_t;
include/asm-mips/types.h:typedef u64 sector_t;
include/asm-ppc/types.h:typedef u64 sector_t;
include/asm-s390/types.h:typedef u64 sector_t;
include/asm-sh/types.h:typedef u64 sector_t;
include/asm-x86_64/types.h:typedef u64 sector_t;
Choosing the 32 bit versions of those I selected
X86 MIPS32 PPC32 ARCH_S390_31 SUPERH
(Yes, X86_64 wouldn't need it except for defining X86. PARISC and SPARC
might want it, not sure about m68k and the other 32 bit architectures.
For that matter, I wonder what SuperH platform will use it. This patch
just shows what has been merged).
===== drivers/block/Kconfig 1.5 vs edited =====
--- 1.5/drivers/block/Kconfig Sun Apr 20 18:21:17 2003
+++ edited/drivers/block/Kconfig Fri Jul 11 02:17:02 2003
@@ -340,7 +340,7 @@
config LBD
bool "Support for Large Block Devices"
- depends on X86
+ depends on X86 || MIPS32 || PPC32 || ARCH_S390_31 || SUPERH
help
Say Y here if you want to attach large (bigger than 2TB) discs to
your machine, or if you want to have a raid or loopback device
next reply other threads:[~2003-07-12 2:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 2:24 Milton Miller [this message]
2003-07-12 2:31 ` Andrew Morton
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=200307120224.h6C2ONNR016854@sullivan.realtime.net \
--to=miltonm@bga.com \
--cc=akpm@digeo.com \
--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
all inboxes | Powered by JetHome®