From: Thierry Reding <thierry.reding@gmail.com>
To: Jingoo Han <jg1.han@samsung.com>
Cc: 'Thierry Reding' <thierry.reding@avionic-design.de>,
linux-pwm@vger.kernel.org
Subject: Re: [PATCH] pwm: pwm-tiehrpwm: add missing __iomem annotation
Date: Wed, 14 Aug 2013 12:48:24 +0200 [thread overview]
Message-ID: <20130814104823.GA14228@ulmo> (raw)
In-Reply-To: <000f01ce8f48$9a60de60$cf229b20$@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]
On Fri, Aug 02, 2013 at 03:22:03PM +0900, Jingoo Han wrote:
> Fix the following sparse warnings:
>
> drivers/pwm/pwm-tiehrpwm.c:144:16: warning: incorrect type in argument 1 (different address spaces)
> drivers/pwm/pwm-tiehrpwm.c:144:16: expected void const volatile [noderef] <asn:2>*addr
> drivers/pwm/pwm-tiehrpwm.c:144:16: got void *
> drivers/pwm/pwm-tiehrpwm.c:149:9: warning: incorrect type in argument 2 (different address spaces)
> drivers/pwm/pwm-tiehrpwm.c:149:9: expected void volatile [noderef] <asn:2>*addr
> drivers/pwm/pwm-tiehrpwm.c:149:9: got void *
> drivers/pwm/pwm-tiehrpwm.c:157:18: warning: incorrect type in argument 1 (different address spaces)
> drivers/pwm/pwm-tiehrpwm.c:157:18: expected void const volatile [noderef] <asn:2>*addr
> drivers/pwm/pwm-tiehrpwm.c:157:18: got void *
> drivers/pwm/pwm-tiehrpwm.c:160:9: warning: incorrect type in argument 2 (different address spaces)
> drivers/pwm/pwm-tiehrpwm.c:160:9: expected void volatile [noderef] <asn:2>*addr
> drivers/pwm/pwm-tiehrpwm.c:160:9: got void *
>
> Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> ---
> drivers/pwm/pwm-tiehrpwm.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Applied, thanks.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-08-14 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 6:22 [PATCH] pwm: pwm-tiehrpwm: add missing __iomem annotation Jingoo Han
2013-08-14 9:46 ` Thierry Reding
2013-08-14 10:48 ` Thierry Reding [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=20130814104823.GA14228@ulmo \
--to=thierry.reding@gmail.com \
--cc=jg1.han@samsung.com \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@avionic-design.de \
/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).