From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: linux-kernel@vger.kernel.org, Vinod Koul <vinod.koul@intel.com>,
Thierry Reding <thierry.reding@avionic-design.de>
Subject: Re: [PATCH 1/1] dma: pl330: Convert to devm_ioremap_resource()
Date: Thu, 31 Jan 2013 08:30:05 +0100 [thread overview]
Message-ID: <20130131073005.GA12469@kroah.com> (raw)
In-Reply-To: <1359616024-11640-1-git-send-email-sachin.kamat@linaro.org>
On Thu, Jan 31, 2013 at 12:37:04PM +0530, Sachin Kamat wrote:
> Use the newly introduced devm_ioremap_resource() instead of
> devm_request_and_ioremap() which provides more consistent error handling.
>
> Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
> Cc: Vinod Koul <vinod.koul@intel.com>
> Cc: Thierry Reding <thierry.reding@avionic-design.de>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
> This change is based against linux-next tree (20130128).
> This change however introduces the followign sparse warning:
> drivers/dma/pl330.c:2883:22: warning: incorrect type in argument 1 (different address spaces)
> drivers/dma/pl330.c:2883:22: expected void const *ptr
> drivers/dma/pl330.c:2883:22: got void [noderef] <asn:2>*base
> drivers/dma/pl330.c:2884:34: warning: incorrect type in argument 1 (different address spaces)
> drivers/dma/pl330.c:2884:34: expected void const *ptr
> drivers/dma/pl330.c:2884:34: got void [noderef] <asn:2>*base
These are known, a patch has been posted for both the kernel and sparse
to fix this up.
thanks,
greg k-h
next prev parent reply other threads:[~2013-01-31 7:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 7:07 [PATCH 1/1] dma: pl330: Convert to devm_ioremap_resource() Sachin Kamat
2013-01-31 7:28 ` Thierry Reding
2013-01-31 8:09 ` Sachin Kamat
2013-01-31 8:13 ` Thierry Reding
2013-01-31 7:30 ` Greg Kroah-Hartman [this message]
2013-01-31 8:12 ` Thierry Reding
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=20130131073005.GA12469@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sachin.kamat@linaro.org \
--cc=thierry.reding@avionic-design.de \
--cc=vinod.koul@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 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.