netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: ssb: Fix DMA-API compilation for non-PCI systems
Date: Tue, 11 Nov 2008 03:56:35 -0500	[thread overview]
Message-ID: <20081111085635.GA6511@infradead.org> (raw)
In-Reply-To: <200811110032.00814.mb@bu3sch.de>

On Tue, Nov 11, 2008 at 12:32:00AM +0100, Michael Buesch wrote:
> On Monday 10 November 2008 23:53:43 David Miller wrote:
> > Then those architectures need to fix their implementations,
> > simply.  They aren't implementing the generic DMA interfaces
> > properly.  Other subsystems do make use of the generic DMA
> > interfaces in this way.
> > 
> > Even something as simple as checking for &pci_bus_type in the
> > dma_*() routines (like powerpc did for quite some time) is
> > enough to fix the problem.
> 
> Yeah, sure. The architectures are broken.
> But the bugreports hit _my_ code. I got pretty tired of forwarding stuff
> to the arch maintainers, so I implemented something that does work in
> every situation. The bugreports stopped immediately (Except this tiny build
> failure that does only hit under rare circumstances).
> 
> DMA is pretty much a mess, if you look at how ever arch does implement the API
> in a slightly different way.

We have tons of PCI drivers using the dma_ routines.  So please report
the broken architecture to get it fixes instead of whining.


      reply	other threads:[~2008-11-11  8:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10 21:52 ssb: Fix DMA-API compilation for non-PCI systems David Miller
2008-11-10 22:07 ` Michael Buesch
2008-11-10 22:53   ` David Miller
2008-11-10 23:32     ` Michael Buesch
2008-11-11  8:56       ` Christoph Hellwig [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=20081111085635.GA6511@infradead.org \
    --to=hch@infradead.org \
    --cc=davem@davemloft.net \
    --cc=mb@bu3sch.de \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).