From: Shuah Khan <shuah.khan@hp.com>
To: ralf@linux-mips.org, kyungmin.park@samsung.com, arnd@arndb.de,
andrzej.p@samsung.com, m.szyprowski@samsung.com
Cc: linux-mips@linux-mips.org, LKML <linux-kernel@vger.kernel.org>,
shuahkhan@gmail.com
Subject: [PATCH RFT RESEND linux-next] mips: dma-mapping: support debug_dma_mapping_error
Date: Fri, 26 Oct 2012 10:01:38 -0600 [thread overview]
Message-ID: <1351267298.4013.12.camel@lorien2> (raw)
In-Reply-To: <1351208193.6851.17.camel@lorien2>
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/mips/include/asm/dma-mapping.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/mips/include/asm/dma-mapping.h b/arch/mips/include/asm/dma-mapping.h
index be39a12..006b43e 100644
--- a/arch/mips/include/asm/dma-mapping.h
+++ b/arch/mips/include/asm/dma-mapping.h
@@ -40,6 +40,8 @@ static inline int dma_supported(struct device *dev, u64 mask)
static inline int dma_mapping_error(struct device *dev, u64 mask)
{
struct dma_map_ops *ops = get_dma_ops(dev);
+
+ debug_dma_mapping_error(dev, mask);
return ops->mapping_error(dev, mask);
}
--
1.7.9.5
next prev parent reply other threads:[~2012-10-26 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 23:36 [PATCH RFT] mips: dma-mapping: support debug_dma_mapping_error Shuah Khan
2012-10-26 16:01 ` Shuah Khan [this message]
2012-10-26 16:45 ` [PATCH RFT RESEND linux-next] " David Daney
2012-10-26 17:06 ` Shuah Khan
2012-10-26 20:07 ` David Daney
2012-10-26 21:51 ` Shuah Khan
2012-10-26 22:31 ` David Daney
2012-10-30 19:58 ` Shuah Khan
2012-11-15 18:21 ` 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=1351267298.4013.12.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=linux-mips@linux-mips.org \
--cc=m.szyprowski@samsung.com \
--cc=ralf@linux-mips.org \
--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