From: Christoph Hellwig <hch@lst.de>
To: linux-fbdev@vger.kernel.org
Subject: [PATCH] ocfb: remove incorrect __iomem annotation
Date: Mon, 17 Aug 2015 08:10:56 +0000 [thread overview]
Message-ID: <1439799056-16509-1-git-send-email-hch@lst.de> (raw)
Make sparse happy:
drivers/video/fbdev/ocfb.c:375:64: sparse: incorrect type in argument 3 (different address spaces)
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
drivers/video/fbdev/ocfb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/video/fbdev/ocfb.c b/drivers/video/fbdev/ocfb.c
index de98196..97f11d2 100644
--- a/drivers/video/fbdev/ocfb.c
+++ b/drivers/video/fbdev/ocfb.c
@@ -62,7 +62,7 @@ struct ocfb_dev {
int little_endian;
/* Physical and virtual addresses of framebuffer */
dma_addr_t fb_phys;
- void __iomem *fb_virt;
+ void *fb_virt;
u32 pseudo_palette[PALETTE_SIZE];
};
--
1.9.1
next reply other threads:[~2015-08-17 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 8:10 Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-24 10:54 [PATCH] ocfb: remove incorrect __iomem annotation Tomi Valkeinen
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=1439799056-16509-1-git-send-email-hch@lst.de \
--to=hch@lst.de \
--cc=linux-fbdev@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;
as well as URLs for NNTP newsgroup(s).