From: "Randy.Dunlap" <rddunlap@osdl.org>
To: adaplas@pol.net, akpm@osdl.org
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: [PATCH 1/11] asiliantfb: eliminate bad section references
Date: Wed, 9 Mar 2005 10:10:55 -0800 [thread overview]
Message-ID: <20050309101055.2ad16211.rddunlap@osdl.org> (raw)
In-Reply-To: <20050309100825.0d77ded8.rddunlap@osdl.org>
asiliantfb refers to __initdata that should be __devinitdata
and calls __init functions that should be __devinit;
Error: ./drivers/video/asiliantfb.o .text refers to 00000000000006ee R_X86_64_32S .init.data+0x00000000000000a0
Error: ./drivers/video/asiliantfb.o .text refers to 0000000000000711 R_X86_64_32S .init.data
Signed-off-by: Randy Dunlap <rddunlap@osdl.org>
diffstat:=
drivers/video/asiliantfb.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff -Naurp ./drivers/video/asiliantfb.c~video_asil_sections ./drivers/video/asiliantfb.c
--- ./drivers/video/asiliantfb.c~video_asil_sections 2005-03-01 23:38:26.000000000 -0800
+++ ./drivers/video/asiliantfb.c 2005-03-07 20:30:12.000000000 -0800
@@ -465,7 +465,7 @@ static struct chips_init_reg chips_init_
{0xd1, 0x01},
};
-static void __init chips_hw_init(struct fb_info *p)
+static void __devinit chips_hw_init(struct fb_info *p)
{
int i;
@@ -488,7 +488,7 @@ static void __init chips_hw_init(struct
write_fr(chips_init_fr[i].addr, chips_init_fr[i].data);
}
-static struct fb_fix_screeninfo asiliantfb_fix __initdata = {
+static struct fb_fix_screeninfo asiliantfb_fix __devinitdata = {
.id = "Asiliant 69000",
.type = FB_TYPE_PACKED_PIXELS,
.visual = FB_VISUAL_PSEUDOCOLOR,
@@ -497,7 +497,7 @@ static struct fb_fix_screeninfo asiliant
.smem_len = 0x200000, /* 2MB */
};
-static struct fb_var_screeninfo asiliantfb_var __initdata = {
+static struct fb_var_screeninfo asiliantfb_var __devinitdata = {
.xres = 640,
.yres = 480,
.xres_virtual = 640,
@@ -518,7 +518,7 @@ static struct fb_var_screeninfo asiliant
.vsync_len = 2,
};
-static void __init init_asiliant(struct fb_info *p, unsigned long addr)
+static void __devinit init_asiliant(struct fb_info *p, unsigned long addr)
{
p->fix = asiliantfb_fix;
p->fix.smem_start = addr;
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-09 18:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 18:08 [PATCH 0/11] framebuffer: eliminate bad section references Randy.Dunlap
2005-03-09 18:10 ` Randy.Dunlap [this message]
2005-03-09 18:11 ` [PATCH 2/11] atyfb: " Randy.Dunlap
2005-03-09 18:15 ` [PATCH 3/11] imsttfb: " Randy.Dunlap
2005-03-09 18:17 ` [PATCH 4/11] kyro: " Randy.Dunlap
2005-03-09 18:18 ` [PATCH 5/11] neofb: " Randy.Dunlap
2005-03-09 18:19 ` [PATCH 6/11] pm2fb: " Randy.Dunlap
2005-03-09 18:23 ` [PATCH 7/11] radeonfb: " Randy.Dunlap
2005-03-09 18:35 ` Torgeir Veimo
2005-03-09 18:59 ` Randy.Dunlap
2005-03-09 18:24 ` [PATCH 8/11] riva: " Randy.Dunlap
2005-03-09 18:25 ` [PATCH 9/11] savagefb: " Randy.Dunlap
2005-03-09 18:26 ` [PATCH 10/11] sis: " Randy.Dunlap
2005-03-09 18:27 ` [PATCH 11/11] tdfxfb: " Randy.Dunlap
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=20050309101055.2ad16211.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).