From: Al Viro <viro@ftp.linux.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
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>,
Roman Zippel <zippel@linux-m68k.org>,
jdike@karaya.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Russell King <rmk@arm.linux.org.uk>
Subject: Re: uninline check_signature()
Date: Tue, 17 Jul 2007 21:38:53 +0100 [thread overview]
Message-ID: <20070717203853.GO21668@ftp.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0707172225260.23024@anakin>
On Tue, Jul 17, 2007 at 10:31:08PM +0200, Geert Uytterhoeven wrote:
> And we'll all live with a check_signature() in our kernel, which is used
> only by a few legacy drivers that depend on ISA || PCI...
>
> OR I'll have to disable HAS_IOMEM on m68k, and invent a new Kconfig
> symbol for lots of other stuff that currently depends on HAS_IOMEM...
Actually... Is there any reason why it's not simply
kmalloc
memcpy_fromio
memcmp
on all targets? Or just a variably-sized auto array, since we never
do it for large stuff, IIRC...
next prev parent reply other threads:[~2007-07-17 20:39 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 ` uninline check_signature() 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
2007-07-17 20:31 ` Geert Uytterhoeven
2007-07-17 20:38 ` Al Viro [this message]
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=20070717203853.GO21668@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--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=rmk@arm.linux.org.uk \
--cc=schwidefsky@de.ibm.com \
--cc=torvalds@linux-foundation.org \
--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 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.