From: "David S. Miller" <davem@redhat.com>
To: hch@caldera.de
Cc: davidm@hpl.hp.com, mmadore@turbolinux.com,
linux-ia64@linuxia64.org, linux-kernel@vger.kernel.org,
torvalds@transmeta.com
Subject: Re: [Linux-ia64] Proper fix for sym53c8xx_2 driver and dma64_addr_t
Date: Wed, 06 Feb 2002 00:29:06 -0800 (PST) [thread overview]
Message-ID: <20020206.002906.94555802.davem@redhat.com> (raw)
In-Reply-To: <20020206092129.A8739@caldera.de>
In-Reply-To: <20020205223804.A22012@caldera.de> <15456.21030.840746.209377@napali.hpl.hp.com> <20020206092129.A8739@caldera.de>
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:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C6043E5.D1F40E5D@turbolinux.com>
[not found] ` <20020205223804.A22012@caldera.de>
[not found] ` <15456.21030.840746.209377@napali.hpl.hp.com>
2002-02-06 8:21 ` [Linux-ia64] Proper fix for sym53c8xx_2 driver and dma64_addr_t 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-05 21:23 ` Gérard Roudier
2002-02-06 17:10 ` Christoph Hellwig
2002-02-06 17:15 ` Christoph Hellwig
2002-02-06 17:15 ` David Mosberger
2002-02-05 21:34 ` Gérard Roudier
2002-02-07 2:09 ` David S. Miller
2002-02-06 21:38 ` Gérard Roudier
2002-02-06 16:54 ` David Mosberger
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=20020206.002906.94555802.davem@redhat.com \
--to=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=hch@caldera.de \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmadore@turbolinux.com \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox