From: Joerg Roedel <joro@8bytes.org>
To: Shuah Khan <shuah.khan@hp.com>
Cc: davem@davemloft.net, kyungmin.park@samsung.com,
m.szyprowski@samsung.com, sam@ravnborg.org, arnd@arndb.de,
sparclinux@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
shuahkhan@gmail.com
Subject: Re: [PATCH RFT] sparc: dma-mapping: support debug_dma_mapping_error
Date: Sat, 17 Nov 2012 13:22:26 +0100 [thread overview]
Message-ID: <20121117122226.GT25742@8bytes.org> (raw)
In-Reply-To: <1351211773.6851.24.camel@lorien2>
On Thu, Oct 25, 2012 at 06:36:13PM -0600, Shuah Khan wrote:
> >From 9e8feb61482288c5a5dd609e0dd17c1a262a48a3 Mon Sep 17 00:00:00 2001
> From: Shuah Khan <shuahkhan@gmail.com>
> Date: Thu, 25 Oct 2012 18:31:42 -0600
> Subject: [PATCH RFT] sparc: dma-mapping: support debug_dma_mapping_error
>
> 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>
Applied to dma-debug, thanks.
Btw, what about the patches for the other archs? They should depend on
the dma-debug branch too and should also be there, no?
Joerg
prev parent reply other threads:[~2012-11-17 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 0:36 [PATCH RFT] sparc: dma-mapping: support debug_dma_mapping_error Shuah Khan
2012-10-26 0:38 ` [PATCH RFT RESEND] " Shuah Khan
2012-10-26 16:13 ` [PATCH RFT RESEND linux-next] " Shuah Khan
2012-10-26 19:01 ` David Miller
2012-10-26 19:10 ` David Miller
2012-10-26 21:40 ` Shuah Khan
2012-11-10 0:38 ` David Miller
2012-11-10 0:52 ` Shuah Khan
2012-11-10 0:54 ` David Miller
2012-11-10 1:21 ` Shuah Khan
2012-11-15 17:39 ` Shuah Khan
2012-11-17 12:22 ` Joerg Roedel [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=20121117122226.GT25742@8bytes.org \
--to=joro@8bytes.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=sam@ravnborg.org \
--cc=shuah.khan@hp.com \
--cc=shuahkhan@gmail.com \
--cc=sparclinux@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).