From: William Lee Irwin III <wli@holomorphy.com>
To: Paul Jackson <pj@sgi.com>
Cc: "David S. Miller" <davem@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Does io_remap_page_range() take 5 or 6 args?
Date: Wed, 18 Aug 2004 14:35:38 -0700 [thread overview]
Message-ID: <20040818213538.GK11200@holomorphy.com> (raw)
In-Reply-To: <20040818141541.467e1e2d.pj@sgi.com>
Dave Miller wrote:
>> Each platform needs different args, unfortunately.
On Wed, Aug 18, 2004 at 02:15:41PM -0700, Paul Jackson wrote:
> Doesn't that make it kinda rough on the folks trying to write
> arch-independent code, such as sound/core/pcm_native.c that I am
> tripping over?
> I can imagine a possible 'solution' something like (1) always passing
> six args, and (2) providing arch-dependent macros to generate those last
> two args, from some arch-generic value.
> Just brainstorming ...
This would not be useful. The extra argument is so that 64-bit values
don't have to be passed. Keeping the minimal number of arguments and
changing its meaning to be a pfn will suffice for the purposes here.
-- wli
prev parent reply other threads:[~2004-08-18 21:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 20:33 Does io_remap_page_range() take 5 or 6 args? Paul Jackson
2004-08-18 20:53 ` William Lee Irwin III
2004-08-18 20:55 ` David S. Miller
2004-08-18 20:56 ` David S. Miller
2004-08-18 21:05 ` William Lee Irwin III
2004-08-18 21:30 ` David S. Miller
2004-08-18 21:40 ` William Lee Irwin III
2004-08-18 22:00 ` William Lee Irwin III
2004-08-18 22:59 ` William Lee Irwin III
2004-08-18 23:16 ` David S. Miller
2004-08-18 23:33 ` William Lee Irwin III
2004-08-19 2:38 ` William Lee Irwin III
2004-08-19 2:43 ` David S. Miller
2004-08-19 2:51 ` William Lee Irwin III
2004-08-18 21:36 ` Richard B. Johnson
2004-08-18 20:54 ` David S. Miller
2004-08-18 21:15 ` Paul Jackson
2004-08-18 21:35 ` William Lee Irwin III [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=20040818213538.GK11200@holomorphy.com \
--to=wli@holomorphy.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
/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.