From: Jeff Garzik <jgarzik@pobox.com>
To: Andi Kleen <ak@muc.de>
Cc: netdev@oss.sgi.com, irda-users@lists.sourceforge.net,
jt@hpl.hp.com, the_nihilant@autistici.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Drop ISA dependencies from IRDA drivers
Date: Thu, 15 Jul 2004 17:00:38 -0400 [thread overview]
Message-ID: <40F6F076.2080001@pobox.com> (raw)
In-Reply-To: <20040715205001.GA2527@muc.de>
Andi Kleen wrote:
> On Thu, Jul 15, 2004 at 12:48:07PM -0400, Jeff Garzik wrote:
>>And with legacy ISA devices still around, I don't see a whole lot of
>>value in differentiating between "I have ISA slots" and "I have ISA
>>devices".
>
>
> There is great value. Basically most ISA drivers are not 64bit
> clean (if they even still work on i386 which is also often doubtful
> in 2.6) and it is a great way for 64bit archs to get rid of a lot
> of not working code.
I file that under "hiding bugs", since it will not be immediately
obvious to a bug hunter or maintainer what the real problem is.
If a driver is broken on 64-bit, please add "&& !64BIT" to the Kconfig.
As you yourself just explained, your wish is to use CONFIG_ISA, but your
intent is only coincedentally related to ISA.
Jeff
next prev parent reply other threads:[~2004-07-15 21:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m34qo96x8m.fsf@averell.firstfloor.org>
2004-07-15 16:48 ` [PATCH] Drop ISA dependencies from IRDA drivers Jeff Garzik
2004-07-15 20:50 ` Andi Kleen
2004-07-15 21:00 ` Jeff Garzik [this message]
2004-07-15 21:55 ` Andi Kleen
2004-07-15 22:32 ` Martin Diehl
2004-07-15 22:42 ` Jean Tourrilhes
2004-07-15 22:57 ` Martin Diehl
2004-07-16 5:45 ` Andi Kleen
2004-07-16 6:19 ` Martin Diehl
2004-07-16 6:19 ` Andi Kleen
2004-07-16 6:33 ` Martin Diehl
2004-07-15 22:35 ` Jean Tourrilhes
2004-07-16 5:36 ` Andi Kleen
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=40F6F076.2080001@pobox.com \
--to=jgarzik@pobox.com \
--cc=ak@muc.de \
--cc=irda-users@lists.sourceforge.net \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=the_nihilant@autistici.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.