From: Linus Torvalds <torvalds@linux-foundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jeff Dike <jdike@addtoit.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
zippel@linux-m68k.org, jdike@karaya.com,
alan@lxorguk.ukuu.org.uk,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: uninline check_signature()
Date: Tue, 17 Jul 2007 11:03:00 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0707171102040.19166@woody.linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707171842590.10600@anakin>
On Tue, 17 Jul 2007, Geert Uytterhoeven wrote:
>
> M68k uses I/O memory for all I/O (hence it sets CONFIG_HAS_IOMEM), but
> many m68k machines don't have PCI or ISA (hence it doesn't set
> CONFIG_PCI resp. CONFIG_ISA).
It doesn't matter whether the machine has PCI or ISA. The only thing that
matters is whether the thing compiles (which in turn depends on whether it
has "readb()", which in turn is what HAS_IOMEM is all about).
So I do think that HAS_IOMEM is the right thing here.
Linus
next prev parent reply other threads:[~2007-07-17 18:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200707161802.l6GI2tNp007390@hera.kernel.org>
2007-07-16 22:12 ` Heiko Carstens
2007-07-16 22:29 ` Andrew Morton
2007-07-16 22:35 ` Linus Torvalds
2007-07-16 23:03 ` Heiko Carstens
2007-07-17 13:22 ` Geert Uytterhoeven
2007-07-17 16:33 ` Jeff Dike
2007-07-17 16:46 ` Geert Uytterhoeven
2007-07-17 18:03 ` Linus Torvalds [this message]
2007-07-17 20:31 ` Geert Uytterhoeven
2007-07-17 20:38 ` Al Viro
2007-07-17 20:40 ` Linus Torvalds
2007-07-18 6:45 ` Geert Uytterhoeven
2007-08-12 10:24 ` [PATCH] Introduce CONFIG_CHECK_SIGNATURE (was: Re: uninline check_signature()) Geert Uytterhoeven
2007-07-17 8:50 ` uninline check_signature() Geert Uytterhoeven
2007-07-17 8:53 ` Geert Uytterhoeven
2007-07-18 11:33 ` Maciej W. Rozycki
2007-07-17 8:59 ` Pekka Enberg
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=alpine.LFD.0.999.0707171102040.19166@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=geert@linux-m68k.org \
--cc=heiko.carstens@de.ibm.com \
--cc=jdike@addtoit.com \
--cc=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=zippel@linux-m68k.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®