From: "David S. Miller" <davem@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: solca@guug.org, zaitcev@redhat.com, linux-kernel@vger.kernel.org,
sparclinux@vger.kernel.org, debian-sparc@lists.debian.org
Subject: Re: sparc scsi esp depends on pci & hangs on boot
Date: Tue, 22 Jul 2003 23:24:10 -0700 [thread overview]
Message-ID: <20030722232410.7a37ed4d.davem@redhat.com> (raw)
In-Reply-To: <20030723070739.A697@infradead.org>
On Wed, 23 Jul 2003 07:07:39 +0100
Christoph Hellwig <hch@infradead.org> wrote:
> Sparc unfortunately defines the new DMA API in terms of the PCI DMA API
> which gets you this mess.
Sparc did not do this, the person coding up the new DMA API
decided it was a good idea to implement the generic version
this way. :-)
I think it's rediculious that I have to implement the whole
new DMA API abstraction thing just to get rid of this PCI
dependency.
Why don't we put the enum dma_direction somewhere else? Some
linux/foo.h header that doesn't require asm/dma*.h
next prev parent reply other threads:[~2003-07-23 6:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 2:51 sparc scsi esp depends on pci & hangs on boot Otto Solares
2003-07-22 12:09 ` Pete Zaitcev
2003-07-22 18:26 ` Otto Solares
2003-07-23 0:54 ` David S. Miller
2003-07-23 2:32 ` Otto Solares
2003-07-23 6:07 ` Christoph Hellwig
2003-07-23 6:24 ` David S. Miller [this message]
2003-07-23 6:28 ` Christoph Hellwig
2003-07-23 6:29 ` David S. Miller
2003-07-23 6:40 ` Christoph Hellwig
2003-07-23 6:57 ` David S. Miller
2003-07-23 7:02 ` Christoph Hellwig
2003-07-23 7:20 ` David S. Miller
2003-07-23 8:45 ` Otto Solares
2003-07-23 14:42 ` Geert Uytterhoeven
2003-07-23 6:43 ` Otto Solares
2003-07-23 7:04 ` Christoph Hellwig
2003-07-23 7:20 ` Otto Solares
2003-07-23 7:27 ` David S. Miller
2003-07-23 8:33 ` C.Newport
2003-07-23 8:28 ` David S. Miller
2003-07-23 9:35 ` C.Newport
2003-07-23 9:37 ` David S. Miller
2003-07-23 8:55 ` Otto Solares
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=20030722232410.7a37ed4d.davem@redhat.com \
--to=davem@redhat.com \
--cc=debian-sparc@lists.debian.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=solca@guug.org \
--cc=sparclinux@vger.kernel.org \
--cc=zaitcev@redhat.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.