From: Shuah Khan <shuah.khan@hp.com>
To: tony.luck@intel.com, m.szyprowski@samsung.com
Cc: fenghua.yu@intel.com, arnd@arndb.de, andrzej.p@samsung.com,
kyungmin.park@samsung.com, linux-ia64@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
shuahkhan@gmail.com
Subject: Re: [PATCH RFT RESEND linux-next] ia64: dma-mapping: support debug_dma_mapping_error
Date: Thu, 15 Nov 2012 11:08:47 -0700 [thread overview]
Message-ID: <1353002927.2532.46.camel@lorien2> (raw)
In-Reply-To: <1351266308.4013.5.camel@lorien2>
On Fri, 2012-10-26 at 09:45 -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/ia64/include/asm/dma-mapping.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/ia64/include/asm/dma-mapping.h b/arch/ia64/include/asm/dma-mapping.h
> index 4f5e814..cf3ab7e 100644
> --- a/arch/ia64/include/asm/dma-mapping.h
> +++ b/arch/ia64/include/asm/dma-mapping.h
> @@ -58,6 +58,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 daddr)
> {
> struct dma_map_ops *ops = platform_dma_get_ops(dev);
> + debug_dma_mapping_error(dev, daddr);
> return ops->mapping_error(dev, daddr);
> }
>
Marek,
This one is for ia64 to go through your tree with all the other arch
debug_dma_mapping_error() patches.
Thanks,
-- Shuah
prev parent reply other threads:[~2012-11-15 18:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 23:21 [PATCH RFT] ia64: dma-mapping: support debug_dma_mapping_error Shuah Khan
2012-10-26 15:45 ` [PATCH RFT RESEND linux-next] " Shuah Khan
2012-11-15 18:08 ` Shuah Khan [this message]
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=1353002927.2532.46.camel@lorien2 \
--to=shuah.khan@hp.com \
--cc=andrzej.p@samsung.com \
--cc=arnd@arndb.de \
--cc=fenghua.yu@intel.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=shuahkhan@gmail.com \
--cc=tony.luck@intel.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