All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Andrew Morton <akpm@osdl.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ppc64: create dma_mapping_error
Date: Thu, 8 Apr 2004 00:30:08 +1000	[thread overview]
Message-ID: <20040407143008.GP26474@krispykreme> (raw)
In-Reply-To: <1080923616.1829.73.camel@mulgrave>


> What exactly are you guys doing?
> 
> The API Anton introduced:  dma_mapping_error() takes only a virtual
> address as the argument (no struct device or anyting), so the additional
> API's pci_dma_mapping_error() and vio_dma_mapping_error have absolutely
> no choice but to do the same thing as dma_mapping_error() (because the
> error return cannot be bus or device specific).

Umm yeah, we should probably just use dma_mapping_error. I want to see
vio_* disappear anyway.

Anton

      reply	other threads:[~2004-04-07 14:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-02 16:33 [PATCH] ppc64: create dma_mapping_error James Bottomley
2004-04-07 14:30 ` Anton Blanchard [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=20040407143008.GP26474@krispykreme \
    --to=anton@samba.org \
    --cc=James.Bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.