From: Andi Kleen <andi@firstfloor.org>
To: Wolfgang Grandegger <public-wg-5Yr1BZd7O62+XT7JhA+gdA@plane.gmane.org>
Cc: public-x86-DgEjT+Ai2ygdnm+yROfE0A@plane.gmane.org,
SocketCAN Core Mailing List
<public-socketcan-core-0fE9KPoRgkgATYTw5x5z8w@plane.gmane.org>,
Willy Lambert
<public-lambert.willy-Re5JQEeQqe8AvxtiuMwx3w@plane.gmane.org>,
LKML <public-linux-kernel-u79uwXL29TY76Z2rM5mHXA@plane.gmane.org>
Subject: Re: [PATCH] x86_64: permit to configure ISA support also for x86_64 systems
Date: Fri, 16 Sep 2011 15:33:32 -0700 [thread overview]
Message-ID: <m2y5xodsn7.fsf@firstfloor.org> (raw)
In-Reply-To: <4E731565.5050307@grandegger.com> (Wolfgang Grandegger's message of "Fri, 16 Sep 2011 11:22:45 +0200")
Wolfgang Grandegger <wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org> writes:
> There are 64-bit systems out there, like the ATOM N450, which
> have ISA slots. This patch is necessary to get the "sja1000_isa"
> Socket-CAN driver working on such systems.
Really bad idea.
You'll get a zillion non 64bit safe unmaintained old ISA
drivers then, a non trivial percentage of them will likely
explode when just loaded.
Not to speak of the warning load at allyesconfig builds.
Maybe define a ISA_64 or so.
But it's really a bad idea.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
prev parent reply other threads:[~2011-09-16 22:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 9:22 [PATCH] x86_64: permit to configure ISA support also for x86_64 systems Wolfgang Grandegger
2011-09-16 19:19 ` Valdis.Kletnieks
2011-09-16 19:31 ` Wolfgang Grandegger
2011-09-20 15:47 ` Arnd Bergmann
2011-09-21 8:33 ` Wolfgang Grandegger
2011-09-21 9:24 ` Arnd Bergmann
2011-09-21 22:13 ` Andi Kleen
2011-09-22 6:43 ` Wolfgang Grandegger
2011-09-22 14:20 ` Arnd Bergmann
2011-09-22 14:57 ` Wolfgang Grandegger
2011-09-18 23:19 ` Calvin Walton
2011-09-16 22:33 ` Andi Kleen [this message]
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=m2y5xodsn7.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=public-lambert.willy-Re5JQEeQqe8AvxtiuMwx3w@plane.gmane.org \
--cc=public-linux-kernel-u79uwXL29TY76Z2rM5mHXA@plane.gmane.org \
--cc=public-socketcan-core-0fE9KPoRgkgATYTw5x5z8w@plane.gmane.org \
--cc=public-wg-5Yr1BZd7O62+XT7JhA+gdA@plane.gmane.org \
--cc=public-x86-DgEjT+Ai2ygdnm+yROfE0A@plane.gmane.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.