From: Archit Taneja <archit@ti.com>
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] fbdev: arm has __raw I/O accessors, use them in fb.h
Date: Fri, 16 Nov 2012 09:28:04 +0000 [thread overview]
Message-ID: <1353057364-21214-1-git-send-email-archit@ti.com> (raw)
This removes the sparse warnings on arm platforms:
warning: cast removes address space of expression
Signed-off-by: Archit Taneja <archit@ti.com>
---
include/linux/fb.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/fb.h b/include/linux/fb.h
index c7a9571..7fce1e1 100644
--- a/include/linux/fb.h
+++ b/include/linux/fb.h
@@ -548,7 +548,7 @@ static inline struct apertures_struct *alloc_apertures(unsigned int max_num) {
#define fb_memcpy_fromfb sbus_memcpy_fromio
#define fb_memcpy_tofb sbus_memcpy_toio
-#elif defined(__i386__) || defined(__alpha__) || defined(__x86_64__) || defined(__hppa__) || defined(__sh__) || defined(__powerpc__) || defined(__avr32__) || defined(__bfin__)
+#elif defined(__i386__) || defined(__alpha__) || defined(__x86_64__) || defined(__hppa__) || defined(__sh__) || defined(__powerpc__) || defined(__avr32__) || defined(__bfin__) || defined(__arm__)
#define fb_readb __raw_readb
#define fb_readw __raw_readw
--
1.7.9.5
next reply other threads:[~2012-11-16 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 9:28 Archit Taneja [this message]
2012-11-16 9:28 ` [RFC] fbdev: arm has __raw I/O accessors, use them in fb.h Tomi Valkeinen
2012-11-16 16:44 ` H Hartley Sweeten
2012-11-19 5:33 ` Archit Taneja
2012-11-19 9:15 ` Russell King - ARM Linux
2012-11-19 9:36 ` Tomi Valkeinen
2012-11-19 9:46 ` Russell King - ARM Linux
2012-11-19 10:34 ` 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=1353057364-21214-1-git-send-email-archit@ti.com \
--to=archit@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).