From: Andi Kleen <ak@suse.de>
To: Matthew Wilcox <willy@debian.org>
Cc: willy@debian.org, linux-kernel@vger.kernel.org
Subject: Re: CONFIG_64_BIT
Date: Tue, 2 Sep 2003 19:52:46 +0200 [thread overview]
Message-ID: <20030902195246.7ba3515c.ak@suse.de> (raw)
In-Reply-To: <20030902174436.GP13467@parcelfarce.linux.theplanet.co.uk>
On Tue, 2 Sep 2003 18:44:36 +0100
Matthew Wilcox <willy@debian.org> wrote:
> On Tue, Sep 02, 2003 at 07:35:11PM +0200, Andi Kleen wrote:
> > Matthew Wilcox <willy@debian.org> writes:
> >
> > > What do people think of CONFIG_64_BIT? It saves us from using
> > > !(IA64 || MIPS64 || PARISC64 || S390X || SPARC64 || X86_64) or
> >
> > For Kconfigs it may make sense, but is there any Config rule that
> > checks for all 64bit archs (opposed to checking for specific archs)?
> > I cannot thinkg of any.
>
> ... that was what the patch added.
It added a symbol that means that, but are there any users for it?
Ok, I2O and ATM and WANPIPE maybe but I assume that both are getting fixed
Still all those are non 64bit safe, so it may be better to have an
CONFIG_32BIT_ONLY or similar.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Tue, 2 Sep 2003 18:44:36 +0100
Matthew Wilcox <willy@debian.org> wrote:
> On Tue, Sep 02, 2003 at 07:35:11PM +0200, Andi Kleen wrote:
> > Matthew Wilcox <willy@debian.org> writes:
> >
> > > What do people think of CONFIG_64_BIT? It saves us from using
> > > !(IA64 || MIPS64 || PARISC64 || S390X || SPARC64 || X86_64) or
> >
> > For Kconfigs it may make sense, but is there any Config rule that
> > checks for all 64bit archs (opposed to checking for specific archs)?
> > I cannot thinkg of any.
>
> ... that was what the patch added.
It added a symbol that means that, but are there any users for it?
Ok, I2O and ATM and WANPIPE maybe but I assume that both are getting fixed
Still all those are non 64bit safe, so it may be better to have an
CONFIG_32BIT_ONLY or similar.
-Andi
next prev parent reply other threads:[~2003-09-02 18:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030902143424.GO13467@parcelfarce.linux.theplanet.co.uk.suse.lists.linux.kernel>
2003-09-02 17:35 ` CONFIG_64_BIT Andi Kleen
2003-09-02 17:44 ` CONFIG_64_BIT Matthew Wilcox
2003-09-02 17:52 ` Andi Kleen [this message]
2003-09-03 13:37 ` CONFIG_64_BIT Alan Cox
2003-09-02 14:34 CONFIG_64_BIT Matthew Wilcox
2003-09-02 17:52 ` CONFIG_64_BIT Jeff Garzik
2003-09-03 8:39 ` CONFIG_64_BIT Geert Uytterhoeven
2003-09-03 10:10 ` CONFIG_64_BIT Andreas Schwab
2003-09-03 10:44 ` CONFIG_64_BIT Wade
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=20030902195246.7ba3515c.ak@suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@debian.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 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.