From: Jinqiang Zeng <jinqiangzeng@gmail.com>
To: Lidza Louina <lidza.louina@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: driverdev-devel@linuxdriverproject.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Jinqiang Zeng <jinqiangzeng@gmail.com>
Subject: [PATCH] dgap: fix sparse warnings
Date: Wed, 14 May 2014 22:41:28 +0800 [thread overview]
Message-ID: <1400078488-22391-1-git-send-email-jinqiangzeng@gmail.com> (raw)
fix the sparse warnings
drivers/staging/dgap/dgap.c:689:28: warning: incorrect type in argument 1 (different address spaces)
drivers/staging/dgap/dgap.c:689:28: expected void volatile [noderef] <asn:2>*addr
drivers/staging/dgap/dgap.c:689:28: got unsigned char [usertype] *re_map_port
drivers/staging/dgap/dgap.c:695:28: warning: incorrect type in argument 1 (different address spaces)
drivers/staging/dgap/dgap.c:695:28: expected void volatile [noderef] <asn:2>*addr
drivers/staging/dgap/dgap.c:695:28: got unsigned char [usertype] *re_map_membase
Signed-off-by: Jinqiang Zeng <jinqiangzeng@gmail.com>
---
drivers/staging/dgap/dgap.h | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/dgap/dgap.h b/drivers/staging/dgap/dgap.h
index 6b8f5f8..bceff7d 100644
--- a/drivers/staging/dgap/dgap.h
+++ b/drivers/staging/dgap/dgap.h
@@ -578,8 +578,8 @@ struct board_t {
ulong membase; /* Start of base memory of the card */
ulong membase_end; /* End of base memory of the card */
- uchar *re_map_port; /* Remapped io port of the card */
- uchar *re_map_membase;/* Remapped memory of the card */
+ uchar __iomem *re_map_port; /* Remapped io port of the card */
+ uchar __iomem *re_map_membase;/* Remapped memory of the card */
uchar runwait; /* # Processes waiting for FEP */
uchar inhibit_poller; /* Tells the poller to leave us alone */
--
1.7.7.6
next reply other threads:[~2014-05-14 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 14:41 Jinqiang Zeng [this message]
2014-05-14 14:53 ` [PATCH] dgap: fix sparse warnings Dan Carpenter
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=1400078488-22391-1-git-send-email-jinqiangzeng@gmail.com \
--to=jinqiangzeng@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=lidza.louina@gmail.com \
--cc=linux-kernel@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