From: Shuah Khan <shuah.khan@hp.com>
To: monstr@monstr.eu
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 RFT] microblaze: dma-mapping: support debug_dma_mapping_error
Date: Fri, 26 Oct 2012 08:58:51 -0600 [thread overview]
Message-ID: <1351263531.2712.3.camel@lorien2> (raw)
In-Reply-To: <508A49D3.2080303@monstr.eu>
On Fri, 2012-10-26 at 10:29 +0200, Michal Simek wrote:
> On 10/26/2012 01:29 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.
> >
> > Signed-off-by: Shuah Khan <shuah.khan@hp.com>
> > ---
> > arch/microblaze/include/asm/dma-mapping.h | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/microblaze/include/asm/dma-mapping.h b/arch/microblaze/include/asm/dma-mapping.h
> > index 01d2282..4451c7a 100644
> > --- a/arch/microblaze/include/asm/dma-mapping.h
> > +++ b/arch/microblaze/include/asm/dma-mapping.h
> > @@ -114,6 +114,7 @@ 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);
>
> here should be empty line.
>
> > + debug_dma_mapping_error(dev, dma_addr);
> > if (ops->mapping_error)
> > return ops->mapping_error(dev, dma_addr);
>
> Patch looks good to me. I was greping the latest mainline tree and I can't see
> reference to debug_dma_mapping_error. Can you tell me where this function
> is implemented.
> I have also seen that you have sent several similar patches like this.
>
> If you want to add it through any other tree here is my ACK:
>
> Acked-by: Michal Simek <monstr@monstr.eu>
>
> I will definitely keep my eyes on it.
debug_dma_mapping_error() patch is in linux-next. I probably should send
all of these patches marked explicitly for linux-next.
Thanks,
-- Shuah
next prev parent reply other threads:[~2012-10-26 14:58 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 [this message]
2012-10-26 15:53 ` [PATCH v2 linux-next] " Shuah Khan
2012-11-15 17:34 ` Shuah Khan
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=1351263531.2712.3.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.