From: David Daney <ddaney.cavm@gmail.com>
To: shuah.khan@hp.com
Cc: ralf@linux-mips.org, kyungmin.park@samsung.com, arnd@arndb.de,
andrzej.p@samsung.com, m.szyprowski@samsung.com,
linux-mips@linux-mips.org, LKML <linux-kernel@vger.kernel.org>,
shuahkhan@gmail.com
Subject: Re: [PATCH RFT RESEND linux-next] mips: dma-mapping: support debug_dma_mapping_error
Date: Fri, 26 Oct 2012 15:31:39 -0700 [thread overview]
Message-ID: <508B0F4B.80601@gmail.com> (raw)
In-Reply-To: <1351288264.6885.11.camel@lorien2>
On 10/26/2012 02:51 PM, Shuah Khan wrote:
>>>> On 10/26/2012 09:01 AM, 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.
I'm confused.
Your claim that a 'warning is generated' seems to be in conflict with...
[...]
> Got it. Thanks. I would volunteer to look at fixing all the problems,
> but unfortunately I don't have a MIPS box handy
This statement that you don't have hardware that exhibits the problem.
How was the patch tested? How do you even know there is a problem?
David Daney
next prev parent reply other threads:[~2012-10-26 22:31 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 ` [PATCH RFT RESEND linux-next] " Shuah Khan
2012-10-26 16:45 ` 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 [this message]
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=508B0F4B.80601@gmail.com \
--to=ddaney.cavm@gmail.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=shuah.khan@hp.com \
--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.