From: Jeff Garzik <jeff@garzik.org>
To: Andi Kleen <ak@suse.de>
Cc: chas@cmf.nrl.navy.mil, netdev@vger.kernel.org, kkeil@suse.de,
kai.germaschewski@gmx.de, isdn4linux@listserv.isdn4linux.de,
mac@melware.de, markus.lidel@shadowconnect.com,
samuel@sortiz.org, Neela.Kolli@engenio.com,
linux-scsi@vger.kernel.org, Greg KH <greg@kroah.com>,
thomas@winischhofer.net
Subject: Re: [PATCH] Introduce BROKEN_ON_64BIT facility
Date: Mon, 02 Oct 2006 05:54:19 -0400 [thread overview]
Message-ID: <4520E1CB.6070104@garzik.org> (raw)
In-Reply-To: <p737izjhwpa.fsf@verdi.suse.de>
Andi Kleen wrote:
> Jeff Garzik <jeff@garzik.org> writes:
>
>> Add a broken-on-64bit option, similar to the existing broken-on-smp
>> config option. This is just the first pass, marking the obvious
>> candidates.
>
> When I had this problem in the past I just used && !64BIT.
> How is this new option different?
Same reason why we have CONFIG_BROKEN_ON_SMP separate from CONFIG_SMP.
> AFAIK I2O got fixed too. Do you have any evidence that it is really
> broken on 64bit?
i2o_config did not. Just read the code, it's obvious...
Jeff
next prev parent reply other threads:[~2006-10-02 9:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 4:55 [PATCH] Introduce BROKEN_ON_64BIT facility Jeff Garzik
2006-10-02 9:51 ` Andi Kleen
2006-10-02 9:54 ` Jeff Garzik [this message]
2006-10-02 14:19 ` Markus Lidel
2006-10-02 13:03 ` Alan Cox
2006-10-02 13:52 ` chas williams - CONTRACTOR
2006-10-02 15:12 ` Alan Cox
2006-10-02 15:18 ` Matthew Wilcox
2006-10-02 16:21 ` 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=4520E1CB.6070104@garzik.org \
--to=jeff@garzik.org \
--cc=Neela.Kolli@engenio.com \
--cc=ak@suse.de \
--cc=chas@cmf.nrl.navy.mil \
--cc=greg@kroah.com \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=kai.germaschewski@gmx.de \
--cc=kkeil@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=mac@melware.de \
--cc=markus.lidel@shadowconnect.com \
--cc=netdev@vger.kernel.org \
--cc=samuel@sortiz.org \
--cc=thomas@winischhofer.net \
/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;
as well as URLs for NNTP newsgroup(s).