linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shuah.khan@hp.com (Shuah Khan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH linux-next] ARM64: dma-mapping: support debug_dma_mapping_error
Date: Fri, 02 Nov 2012 09:58:53 -0600	[thread overview]
Message-ID: <1351871933.2721.10.camel@lorien2> (raw)
In-Reply-To: <1351264983.2712.14.camel@lorien2>

On Fri, 2012-10-26 at 09:23 -0600, Shuah Khan wrote:
> Add support for debug_dma_mapping_error() call to avoid warning from
> debug_dma_unmap() interface when it checks for mapping error checked
> status. Without this patch, device driver failed to check map error
> warning is generated. 
> 
> Signed-off-by: Shuah Khan <shuah.khan@hp.com>
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>

Do you want this patch going through linux-next or the ARM64 tree? Let
me know your preference.

-- Shuah
> ---
>  arch/arm64/include/asm/dma-mapping.h |    1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm64/include/asm/dma-mapping.h b/arch/arm64/include/asm/dma-mapping.h
> index 538f4b4..9947768 100644
> --- a/arch/arm64/include/asm/dma-mapping.h
> +++ b/arch/arm64/include/asm/dma-mapping.h
> @@ -50,6 +50,7 @@ static inline phys_addr_t dma_to_phys(struct device *dev, dma_addr_t dev_addr)
>  static inline int dma_mapping_error(struct device *dev, dma_addr_t dev_addr)
>  {
>  	struct dma_map_ops *ops = get_dma_ops(dev);
> +	debug_dma_mapping_error(dev, dev_addr);
>  	return ops->mapping_error(dev, dev_addr);
>  }
>  

  reply	other threads:[~2012-11-02 15:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-25 22:47 [PATCH RFT] ARM64: dma-mapping: support debug_dma_mapping_error Shuah Khan
2012-10-26  8:38 ` Santosh Shilimkar
2012-10-26 14:48 ` Catalin Marinas
2012-10-26 15:23   ` [PATCH linux-next] " Shuah Khan
2012-11-02 15:58     ` Shuah Khan [this message]
2012-11-05 16:46       ` Catalin Marinas
2012-11-15 17:11         ` Shuah Khan

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=1351871933.2721.10.camel@lorien2 \
    --to=shuah.khan@hp.com \
    --cc=linux-arm-kernel@lists.infradead.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).