From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: linux-kernel@vger.kernel.org
Cc: adaplas@pol.net, ralf@linux-mips.org
Subject: [PATCH] add __force tag to fb_readb, etc.
Date: Sat, 18 Feb 2006 00:04:08 +0900 (JST) [thread overview]
Message-ID: <20060218.000408.07643246.anemo@mba.ocn.ne.jp> (raw)
This patch fixes many sparse warnings on MIPS (and some other) platform.
Signed-off-by: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
diff --git a/include/linux/fb.h b/include/linux/fb.h
index 2cb19e6..61562d7 100644
--- a/include/linux/fb.h
+++ b/include/linux/fb.h
@@ -823,14 +823,14 @@ struct fb_info {
#else
-#define fb_readb(addr) (*(volatile u8 *) (addr))
-#define fb_readw(addr) (*(volatile u16 *) (addr))
-#define fb_readl(addr) (*(volatile u32 *) (addr))
-#define fb_readq(addr) (*(volatile u64 *) (addr))
-#define fb_writeb(b,addr) (*(volatile u8 *) (addr) = (b))
-#define fb_writew(b,addr) (*(volatile u16 *) (addr) = (b))
-#define fb_writel(b,addr) (*(volatile u32 *) (addr) = (b))
-#define fb_writeq(b,addr) (*(volatile u64 *) (addr) = (b))
+#define fb_readb(addr) (*(volatile u8 __force *) (addr))
+#define fb_readw(addr) (*(volatile u16 __force *) (addr))
+#define fb_readl(addr) (*(volatile u32 __force *) (addr))
+#define fb_readq(addr) (*(volatile u64 __force *) (addr))
+#define fb_writeb(b,addr) (*(volatile u8 __force *) (addr) = (b))
+#define fb_writew(b,addr) (*(volatile u16 __force *) (addr) = (b))
+#define fb_writel(b,addr) (*(volatile u32 __force *) (addr) = (b))
+#define fb_writeq(b,addr) (*(volatile u64 __force *) (addr) = (b))
#define fb_memset memset
#endif
next reply other threads:[~2006-02-17 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 15:04 Atsushi Nemoto [this message]
2006-02-17 16:12 ` Al Viro
2006-02-17 16:33 ` Atsushi Nemoto
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=20060218.000408.07643246.anemo@mba.ocn.ne.jp \
--to=anemo@mba.ocn.ne.jp \
--cc=adaplas@pol.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.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
all inboxes | Powered by JetHome®