From: Andi Kleen <ak@suse.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: Paul Menage <menage@google.com>,
discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] RFC: let x86_64 no longer define X86
Date: Fri, 19 Nov 2004 13:40:55 +0100 [thread overview]
Message-ID: <20041119124055.GG21483@wotan.suse.de> (raw)
In-Reply-To: <20041119122827.GB22981@stusta.de>
> The most important improvement would be to prevent such bugs and to have
> the X86_64 dependency explicitely stated.
This would just end up with me having to hunt through all the drivers
all the time and enabling drivers that need to be enabled on x86-64 too.
It's much easier to disable the few drivers that are broken with !X86_64.
Again please don't do it. It will just cause more work long term.
-Andi
next prev parent reply other threads:[~2004-11-19 12:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 0:51 Adrian Bunk
2004-11-19 1:14 ` Nick Piggin
2004-11-19 1:19 ` Adrian Bunk
2004-11-19 1:31 ` [discuss] " Paul Menage
2004-11-19 12:28 ` Adrian Bunk
2004-11-19 12:40 ` Andi Kleen [this message]
2004-11-19 13:29 ` Adrian Bunk
2004-11-19 8:51 ` Andi Kleen
2004-11-19 10:21 ` Jeff Garzik
2004-11-19 10:34 ` [discuss] " Andi Kleen
2004-11-19 11:28 ` David Woodhouse
2004-11-19 11:55 ` Andi Kleen
2004-11-19 11:50 ` David Woodhouse
2004-11-19 12:05 ` Andi Kleen
2004-11-19 12:12 ` Jeff Garzik
2004-11-19 12:19 ` Andi Kleen
2004-11-19 12:37 ` Jeff Garzik
2004-11-19 12:45 ` Adrian Bunk
2004-11-19 12:55 ` linux-os
2004-11-19 13:04 ` Jeff Garzik
2004-11-19 13:35 ` Raul Miller
2004-11-19 14:11 ` Adrian Bunk
2004-11-19 13:58 ` David Woodhouse
2004-11-19 12:05 ` Adrian Bunk
2004-11-19 12:09 ` Andi Kleen
2004-11-19 11:18 ` Takashi Iwai
2004-11-19 22:31 ` Paul Mackerras
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=20041119124055.GG21483@wotan.suse.de \
--to=ak@suse.de \
--cc=bunk@stusta.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome