All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Damian Hobson-Garcia <dhobsong@igel.co.jp>
Cc: linux-parisc@vger.kernel.org
Subject: Re: [RFC/PATCH 3/4] parisc: Provide default implementation for dma_{alloc,free}_attrs
Date: Sun, 28 Apr 2013 22:06:53 +0200	[thread overview]
Message-ID: <517D815D.2070207@gmx.de> (raw)
In-Reply-To: <1366607407-3103-1-git-send-email-dhobsong@igel.co.jp>

On 04/22/2013 07:10 AM, Damian Hobson-Garcia wrote:
> Most architectures that define CONFIG_HAVE_DMA, have implementations for
> both dma_alloc_attrs() and dma_free_attrs().  All achitectures that do
> not define CONFIG_HAVE_DMA also have both of these definitions provided by
> dma-mapping-broken.h.
> 
> Add default implementations for these functions on parisc.
> 
> Signed-off-by: Damian Hobson-Garcia <dhobsong@igel.co.jp>

Thanks!
Queued up in the parisc tree for 3.10

Helge

> ---
>  arch/parisc/include/asm/dma-mapping.h |    3 +++
>  1 files changed, 3 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/parisc/include/asm/dma-mapping.h b/arch/parisc/include/asm/dma-mapping.h
> index 106b395..d0eae5f 100644
> --- a/arch/parisc/include/asm/dma-mapping.h
> +++ b/arch/parisc/include/asm/dma-mapping.h
> @@ -46,6 +46,9 @@ extern struct hppa_dma_ops pcx_dma_ops;
>  
>  extern struct hppa_dma_ops *hppa_dma_ops;
>  
> +#define dma_alloc_attrs(d, s, h, f, a) dma_alloc_coherent(d, s, h, f)
> +#define dma_free_attrs(d, s, h, f, a) dma_free_coherent(d, s, h, f)
> +
>  static inline void *
>  dma_alloc_coherent(struct device *dev, size_t size, dma_addr_t *dma_handle,
>  		   gfp_t flag)
> 


      reply	other threads:[~2013-04-28 20:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22  5:10 [RFC/PATCH 3/4] parisc: Provide default implementation for dma_{alloc,free}_attrs Damian Hobson-Garcia
2013-04-28 20:06 ` Helge Deller [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=517D815D.2070207@gmx.de \
    --to=deller@gmx.de \
    --cc=dhobsong@igel.co.jp \
    --cc=linux-parisc@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 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.