From: Sam Ravnborg <sam@ravnborg.org>
To: 7eggert@gmx.de
Cc: Arjan van de Ven <arjan@infradead.org>,
Dave Jones <davej@redhat.com>,
linux-ide@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: tighten ATA kconfig dependancies
Date: Sun, 16 Jul 2006 07:58:57 +0200 [thread overview]
Message-ID: <20060716055857.GA29733@mars.ravnborg.org> (raw)
In-Reply-To: <E1G1p1y-0000ZU-Io@be1.lrz>
On Sat, Jul 15, 2006 at 08:38:01PM +0200, Bodo Eggert wrote:
> >> A lot of prehistoric junk shows up on x86-64 configs.
> >
> > ... but in general it helps compile testing if you're hacking stuff;
> > if your hacking IDE on x86-64 you now have to compile 32 bit as well to
> > see if you didn't break the compile for these as well
> >
> > So please don't do this, just disable them in your config...
>
> If you want to compile test these drivers, just revert the patch or edit
> the .config.
Editing .config will not do the trick. kconfig will make sure the kernel
is build with a valid config so they will get turned off.
A cross compile toolchain is the only real soluion. Otherwise we would
soon end up with far to many drivers selectable for x84-64.
Sam
next prev parent reply other threads:[~2006-07-16 5:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6yL2J-7rR-1@gated-at.bofh.it>
[not found] ` <6yLco-7DB-1@gated-at.bofh.it>
2006-07-15 18:38 ` Bodo Eggert
2006-07-16 5:58 ` Sam Ravnborg [this message]
2006-07-16 6:04 ` Arjan van de Ven
2006-07-16 6:17 ` Sam Ravnborg
2006-07-16 18:14 Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2006-07-15 5:34 Dave Jones
2006-07-15 5:49 ` Arjan van de Ven
2006-07-15 6:38 ` Sam Ravnborg
2006-07-15 6:45 ` Arjan van de Ven
2006-07-15 10:28 ` Adrian Bunk
2006-07-15 10:56 ` Arjan van de Ven
2006-07-16 9:13 ` Adrian Bunk
2006-07-24 3:05 ` Alan Cox
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=20060716055857.GA29733@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=7eggert@gmx.de \
--cc=arjan@infradead.org \
--cc=davej@redhat.com \
--cc=linux-ide@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
all inboxes | Powered by JetHome®