From: Arnd Bergmann <arnd@arndb.de>
To: Valdis.Kletnieks@vt.edu
Cc: "Miguel Botón" <mboton.lkml@gmail.com>,
linux-kernel@vger.kernel.org, "Ingo Molnar" <mingo@elte.hu>,
tglx@linutronix.de
Subject: Re: [PATCH] x86: ioport_{32|64}.c unification
Date: Sun, 6 Jan 2008 16:30:09 +0100 [thread overview]
Message-ID: <200801061630.10265.arnd@arndb.de> (raw)
In-Reply-To: <26046.1199598953@turing-police.cc.vt.edu>
On Sunday 06 January 2008, Valdis.Kletnieks@vt.edu wrote:
> You'll still need some ad-croc ifdef-ery at the call site to make it use
> the correct prototype (unless you can come up with some clever way of making
> the two use the same prototype, possibly by passing a dummy argument on
> some architectures...
The call site is the sys_call_table, and user space already has different
calling conventions here, which is the whole reason for this mess.
Arnd <><
prev parent reply other threads:[~2008-01-06 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 23:59 [PATCH] x86: ioport_{32|64}.c unification Miguel Botón
2008-01-06 0:47 ` Arnd Bergmann
2008-01-06 1:00 ` Miguel Botón
2008-01-06 1:20 ` Miguel Botón
2008-01-06 5:55 ` Valdis.Kletnieks
2008-01-06 15:30 ` Arnd Bergmann [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=200801061630.10265.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mboton.lkml@gmail.com \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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.