From: John de la Garza <john@jjdev.com>
To: linux-kernel@vger.kernel.org
Cc: standby24x7@gmail.com, gregkh@linuxfoundation.org
Subject: [PATCH] drivers:staging:crystalhd Fixes sparse warning about incorrect type
Date: Sat, 22 Mar 2014 13:59:10 -0700 [thread overview]
Message-ID: <20140322205907.GA4535@vega.socal.rr.com> (raw)
Fixes these sparse warnings:
drivers/staging/crystalhd/crystalhd_lnx.c:507:30: warning: incorrect type in argument 1 (different address spaces)
drivers/staging/crystalhd/crystalhd_lnx.c:507:30: expected void volatile [noderef] <asn:2>*addr
drivers/staging/crystalhd/crystalhd_lnx.c:507:30: got void *addr
drivers/staging/crystalhd/crystalhd_lnx.c:510:30: warning: incorrect type in argument 1 (different address spaces)
drivers/staging/crystalhd/crystalhd_lnx.c:510:30: expected void volatile [noderef] <asn:2>*addr
drivers/staging/crystalhd/crystalhd_lnx.c:510:30: got void *i2o_addr
Signed-off-by: John de la Garza <john@jjdev.com>
---
drivers/staging/crystalhd/crystalhd_lnx.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/crystalhd/crystalhd_lnx.h b/drivers/staging/crystalhd/crystalhd_lnx.h
index 816e1cd..49e1ef3 100644
--- a/drivers/staging/crystalhd/crystalhd_lnx.h
+++ b/drivers/staging/crystalhd/crystalhd_lnx.h
@@ -58,11 +58,11 @@ struct crystalhd_adp {
unsigned long pci_mem_start;
uint32_t pci_mem_len;
- void *addr;
+ void __iomem *addr;
unsigned long pci_i2o_start;
uint32_t pci_i2o_len;
- void *i2o_addr;
+ void __iomem *i2o_addr;
unsigned int drv_data;
unsigned int dmabits; /* 32 | 64 */
--
1.9.0
reply other threads:[~2014-03-22 20:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140322205907.GA4535@vega.socal.rr.com \
--to=john@jjdev.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=standby24x7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome