From: "David S. Miller" <davem@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Proper fix for sym53c8xx_2 driver and dma64_addr_t
Date: Wed, 06 Feb 2002 08:29:06 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805999@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805991@msgid-missing>
From: Christoph Hellwig <hch@caldera.de>
Date: Wed, 6 Feb 2002 09:21:29 +0100
On Tue, Feb 05, 2002 at 01:44:06PM -0800, David Mosberger wrote:
> Christoph> IA64 needs to define dma64_addr_t.
>
> Not before the driver writers understand when to use it.
Architecture maintainers are not supposed to decide whether driver
writers understand APIs. The dma64_addr_t type is part of the PCI
DMA interface and IA64 needs to defines it.
You do have a point, but so does David.
What driver wants to get at this type and what are they using it
for? dma_addr_t should be used by every driver I am aware of
except the clustering PCI cards I've been told about and that
driver isn't in the kernel at this time.
So who needs it? :-)
next prev parent reply other threads:[~2002-02-06 8:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 20:43 [Linux-ia64] Proper fix for sym53c8xx_2 driver and dma64_addr_t Michael Madore
2002-02-05 21:23 ` Gérard Roudier
2002-02-05 21:26 ` David Mosberger
2002-02-05 21:34 ` Gérard Roudier
2002-02-05 21:38 ` Christoph Hellwig
2002-02-05 21:44 ` David Mosberger
2002-02-06 8:21 ` Christoph Hellwig
2002-02-06 8:29 ` David S. Miller [this message]
2002-02-06 8:35 ` Christoph Hellwig
2002-02-06 8:45 ` David S. Miller
2002-02-06 16:54 ` David Mosberger
2002-02-06 17:10 ` Christoph Hellwig
2002-02-06 17:15 ` Christoph Hellwig
2002-02-06 17:15 ` David Mosberger
2002-02-06 21:38 ` Gérard Roudier
2002-02-07 2:09 ` David S. Miller
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=marc-linux-ia64-105590698805999@msgid-missing \
--to=davem@redhat.com \
--cc=linux-ia64@vger.kernel.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