From: Shuah Khan <shuah.khan@hp.com>
To: rth@twiddle.net, m.szyprowski@samsung.com
Cc: ink@jurassic.park.msu.ru, mattst88@gmail.com,
kyungmin.park@samsung.com, arnd@arndb.de, andrzej.p@samsung.com,
linux-alpha@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
shuahkhan@gmail.com
Subject: Re: [PATCH RFT linux-next] alpha: dma-mapping: support debug_dma_mapping_error
Date: Thu, 15 Nov 2012 10:49:28 -0700 [thread overview]
Message-ID: <1353001768.2532.31.camel@lorien2> (raw)
In-Reply-To: <1351269163.4013.27.camel@lorien2>
On Fri, 2012-10-26 at 10:32 -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/alpha/include/asm/dma-mapping.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/alpha/include/asm/dma-mapping.h b/arch/alpha/include/asm/dma-mapping.h
> index dfa32f0..b4d483b 100644
> --- a/arch/alpha/include/asm/dma-mapping.h
> +++ b/arch/alpha/include/asm/dma-mapping.h
> @@ -32,6 +32,7 @@ static inline void dma_free_attrs(struct device *dev, size_t size,
>
> static inline int dma_mapping_error(struct device *dev, dma_addr_t dma_addr)
> {
> + debug_dma_mapping_error(dev, dma_addr);
> return get_dma_ops(dev)->mapping_error(dev, dma_addr);
> }
>
Marek,
This is for alpha to go through your tree.
-- Shuah
next prev parent reply other threads:[~2012-11-15 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 16:32 [PATCH RFT linux-next] alpha: dma-mapping: support debug_dma_mapping_error Shuah Khan
2012-11-15 17:49 ` Shuah Khan [this message]
2013-03-27 6:59 ` Michael Cree
2013-03-27 15:45 ` Marek Szyprowski
2013-03-27 16:18 ` 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=1353001768.2532.31.camel@lorien2 \
--to=shuah.khan@hp.com \
--cc=andrzej.p@samsung.com \
--cc=arnd@arndb.de \
--cc=ink@jurassic.park.msu.ru \
--cc=kyungmin.park@samsung.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mattst88@gmail.com \
--cc=rth@twiddle.net \
--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