From: Shuah Khan <shuah.khan@hp.com>
To: monstr@monstr.eu, Marek Szyprowski <m.szyprowski@samsung.com>
Cc: kyungmin.park@samsung.com, m.szyprowski@samsung.com,
arnd@arndb.de, andrzej.p@samsung.com,
microblaze-uclinux@itee.uq.edu.au,
LKML <linux-kernel@vger.kernel.org>,
shuahkhan@gmail.com
Subject: Re: [PATCH v2 linux-next] microblaze: dma-mapping: support debug_dma_mapping_error
Date: Thu, 15 Nov 2012 10:34:51 -0700 [thread overview]
Message-ID: <1353000891.2532.22.camel@lorien2> (raw)
In-Reply-To: <1351266812.4013.8.camel@lorien2>
On Fri, 2012-10-26 at 09:53 -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: Michal Simek <monstr@monstr.eu>
Marek,
This is for microblaze to go through your tree.
Thanks,
-- Shuah
> ---
> arch/microblaze/include/asm/dma-mapping.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/microblaze/include/asm/dma-mapping.h b/arch/microblaze/include/asm/dma-mapping.h
> index 01d2282..46460f1 100644
> --- a/arch/microblaze/include/asm/dma-mapping.h
> +++ b/arch/microblaze/include/asm/dma-mapping.h
> @@ -114,6 +114,8 @@ static inline void __dma_sync(unsigned long paddr,
> static inline int dma_mapping_error(struct device *dev, dma_addr_t dma_addr)
> {
> struct dma_map_ops *ops = get_dma_ops(dev);
> +
> + debug_dma_mapping_error(dev, dma_addr);
> if (ops->mapping_error)
> return ops->mapping_error(dev, dma_addr);
>
next prev parent reply other threads:[~2012-11-15 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 23:29 [PATCH RFT] microblaze: dma-mapping: support debug_dma_mapping_error Shuah Khan
2012-10-26 8:29 ` Michal Simek
2012-10-26 14:58 ` Shuah Khan
2012-10-26 15:53 ` [PATCH v2 linux-next] " Shuah Khan
2012-11-15 17:34 ` Shuah Khan [this message]
2012-10-26 15:57 ` [PATCH RFT] " Michal Simek
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=1353000891.2532.22.camel@lorien2 \
--to=shuah.khan@hp.com \
--cc=andrzej.p@samsung.com \
--cc=arnd@arndb.de \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=monstr@monstr.eu \
--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 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.