From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Russell King <rmk@arm.linux.org.uk>
Subject: [PATCH 9/15] fbdev: Add __iomem annotations to cyber2000fb
Date: Fri, 29 Oct 2004 09:58:43 +0800 [thread overview]
Message-ID: <200410290958.43035.adaplas@hotpop.com> (raw)
Add __iomem annotations to cyber2000fb
Signed-off-by: Antonino Daplas <adaplas@pol.net>
---
cyber2000fb.c | 4 ++--
cyber2000fb.h | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff -Nru a/drivers/video/cyber2000fb.c b/drivers/video/cyber2000fb.c
--- a/drivers/video/cyber2000fb.c 2004-10-27 14:58:07 +08:00
+++ b/drivers/video/cyber2000fb.c 2004-10-28 22:57:58 +08:00
@@ -66,8 +66,8 @@
struct display_switch *dispsw;
struct display *display;
struct pci_dev *dev;
- unsigned char *region;
- unsigned char *regs;
+ unsigned char __iomem *region;
+ unsigned char __iomem *regs;
u_int id;
int func_use_count;
u_long ref_ps;
diff -Nru a/drivers/video/cyber2000fb.h b/drivers/video/cyber2000fb.h
--- a/drivers/video/cyber2000fb.h 2004-10-19 20:21:33 +08:00
+++ b/drivers/video/cyber2000fb.h 2004-10-28 22:57:58 +08:00
@@ -466,8 +466,8 @@
struct cyberpro_info {
struct pci_dev *dev;
- unsigned char *regs;
- char *fb;
+ unsigned char __iomem *regs;
+ char __iomem *fb;
char dev_name[32];
unsigned int fb_size;
unsigned int chip_id;
-------------------------------------------------------
This Newsletter Sponsored by: Macrovision
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
reply other threads:[~2004-10-29 2:01 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=200410290958.43035.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=rmk@arm.linux.org.uk \
/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).