From: "David S. Miller" <davem@redhat.com>
To: rmk@arm.linux.org.uk
Cc: porter@cox.net, linux-kernel@vger.kernel.org
Subject: Re: *dma_sync_single API change to support non-coherent cpus
Date: Mon, 03 Mar 2003 11:47:23 -0800 (PST) [thread overview]
Message-ID: <20030303.114723.65560821.davem@redhat.com> (raw)
In-Reply-To: <20030303195825.C17997@flint.arm.linux.org.uk>
From: Russell King <rmk@arm.linux.org.uk>
Date: Mon, 3 Mar 2003 19:58:25 +0000
DaveM, as the author of the original PCI DMA API, any comments on this
(probably ill-thoughtout) idea?
Maybe a better idea is to kill map_single() altogether, and use
scatterlists everywhere.
Long term this is the kind of consolidation that ought to
happen anyways.
And then the implementation can stick whatever it wants in there.
next prev parent reply other threads:[~2003-03-03 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 18:18 *dma_sync_single API change to support non-coherent cpus Matt Porter
2003-03-03 19:58 ` Russell King
2003-03-03 19:47 ` David S. Miller [this message]
2003-03-03 21:40 ` Matt Porter
2003-03-03 21:34 ` Matt Porter
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=20030303.114723.65560821.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=porter@cox.net \
--cc=rmk@arm.linux.org.uk \
/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