From: Shuah Khan <shuah.khan@hp.com>
To: msalter@redhat.com, Andrew Morton <akpm@linux-foundation.org>
Cc: a-jacquiot@ti.com, linux-c6x-dev@linux-c6x.org,
LKML <linux-kernel@vger.kernel.org>,
shuahkhan@gmail.com
Subject: Re: [PATCH RFT RESEND linux-next] c6x: dma-mapping: support debug_dma_mapping_error
Date: Fri, 02 Nov 2012 10:44:15 -0600 [thread overview]
Message-ID: <1351874655.2721.16.camel@lorien2> (raw)
In-Reply-To: <1351266055.4013.1.camel@lorien2>
On Fri, 2012-10-26 at 09:40 -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>
> ---
> arch/c6x/include/asm/dma-mapping.h | 1 +
> 1 file changed, 1 insertion(+)
Would you like to this patch go through c6x arch tree or linux-next?
Please let me know your preference.
-- Shuah
>
> diff --git a/arch/c6x/include/asm/dma-mapping.h b/arch/c6x/include/asm/dma-mapping.h
> index 03579fd..3c69406 100644
> --- a/arch/c6x/include/asm/dma-mapping.h
> +++ b/arch/c6x/include/asm/dma-mapping.h
> @@ -32,6 +32,7 @@ static inline int dma_set_mask(struct device *dev, u64 dma_mask)
> */
> static inline int dma_mapping_error(struct device *dev, dma_addr_t dma_addr)
> {
> + debug_dma_mapping_error(dev, dma_addr);
> return dma_addr == ~0;
> }
>
next prev parent reply other threads:[~2012-11-02 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 23:01 [PATCH RFT] c6x: dma-mapping: support debug_dma_mapping_error Shuah Khan
2012-10-26 15:40 ` [PATCH RFT RESEND linux-next] " Shuah Khan
2012-11-02 16:44 ` Shuah Khan [this message]
2012-11-02 19:10 ` Mark Salter
2012-11-02 19:53 ` Shuah Khan
2012-11-02 20:15 ` Mark Salter
2012-11-02 20:26 ` Shuah Khan
2012-11-02 20:59 ` Mark Salter
2012-11-02 21:08 ` Shuah Khan
2012-11-15 17:45 ` Shuah Khan
2012-11-15 18:02 ` Mark Salter
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=1351874655.2721.16.camel@lorien2 \
--to=shuah.khan@hp.com \
--cc=a-jacquiot@ti.com \
--cc=akpm@linux-foundation.org \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msalter@redhat.com \
--cc=shuahkhan@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox