linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: adaplas@pol.net, akpm@osdl.org
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: [PATCH 6/11] pm2fb: eliminate bad section references
Date: Wed, 9 Mar 2005 10:19:15 -0800	[thread overview]
Message-ID: <20050309101915.6d7b7ea6.rddunlap@osdl.org> (raw)
In-Reply-To: <20050309100825.0d77ded8.rddunlap@osdl.org>


Fix pm2fb section references by changing referenced
  __initdata to __devinitdata.

Error: ./drivers/video/pm2fb.o .text refers to 0000000000000ad4 R_X86_64_PC32     .init.data+0x0000000000000007
Error: ./drivers/video/pm2fb.o .text refers to 0000000000000afc R_X86_64_PC32     .init.data+0x0000000000000003
Error: ./drivers/video/pm2fb.o .text refers to 000000000000147e R_X86_64_PC32     .init.data+0x00000000000000bc
Error: ./drivers/video/pm2fb.o .text refers to 0000000000001491 R_X86_64_PC32     .init.data+0x00000000000000c2
Error: ./drivers/video/pm2fb.o .text refers to 000000000000149a R_X86_64_PC32     .init.data+0x00000000000000bc
Error: ./drivers/video/pm2fb.o .text refers to 00000000000014aa R_X86_64_32S      .init.data+0x00000000000000c0
Error: ./drivers/video/pm2fb.o .text refers to 00000000000014e0 R_X86_64_PC32     .init.data+0x00000000000000f8
Error: ./drivers/video/pm2fb.o .text refers to 00000000000014eb R_X86_64_PC32     .init.data+0x00000000000000f4
Error: ./drivers/video/pm2fb.o .text refers to 000000000000150e R_X86_64_PC32     .init.data+0x00000000000000fc
Error: ./drivers/video/pm2fb.o .text refers to 0000000000001515 R_X86_64_PC32     .init.data+0x00000000000000f4
Error: ./drivers/video/pm2fb.o .text refers to 000000000000152d R_X86_64_32S      .init.data+0x00000000000000c0
Error: ./drivers/video/pm2fb.o .text refers to 00000000000015ce R_X86_64_PC32     .init.data+0x00000000000000cc
Error: ./drivers/video/pm2fb.o .text refers to 00000000000015d7 R_X86_64_PC32     .init.data+0x00000000000000d4
Error: ./drivers/video/pm2fb.o .text refers to 00000000000015fa R_X86_64_PC32     .init.data+0x00000000000000d4
Error: ./drivers/video/pm2fb.o .text refers to 0000000000001601 R_X86_64_PC32     .init.data+0x00000000000000cc
Error: ./drivers/video/pm2fb.o .text refers to 0000000000001644 R_X86_64_32S      .init.data+0x00000000000000c0
Error: ./drivers/video/pm2fb.o .text refers to 0000000000001674 R_X86_64_PC32     .init.data+0xfffffffffffffffc
Error: ./drivers/video/pm2fb.o .text refers to 000000000000168e R_X86_64_PC32     .init.data+0xfffffffffffffffc
Error: ./drivers/video/pm2fb.o .text refers to 00000000000016af R_X86_64_32S      .init.data+0x0000000000000020
Error: ./drivers/video/pm2fb.o .text refers to 0000000000001724 R_X86_64_PC32     .init.data+0x00000000000000d4
Error: ./drivers/video/pm2fb.o .text refers to 000000000000172b R_X86_64_PC32     .init.data+0x00000000000000cc
Error: ./drivers/video/pm2fb.o .text refers to 0000000000001746 R_X86_64_PC32     .init.data+0x00000000000000fc
Error: ./drivers/video/pm2fb.o .text refers to 000000000000174d R_X86_64_PC32     .init.data+0x00000000000000f4

Signed-off-by: Randy Dunlap <rddunlap@osdl.org>

diffstat:=
 drivers/video/pm2fb.c |   10 +++++-----
 1 files changed, 5 insertions(+), 5 deletions(-)

diff -Naurp ./drivers/video/pm2fb.c~video_pm2fb_sections ./drivers/video/pm2fb.c
--- ./drivers/video/pm2fb.c~video_pm2fb_sections	2005-03-01 23:38:33.000000000 -0800
+++ ./drivers/video/pm2fb.c	2005-03-08 13:51:26.000000000 -0800
@@ -62,7 +62,7 @@
 /*
  * Driver data 
  */
-static char *mode __initdata = NULL;
+static char *mode __devinitdata = NULL;
 
 /*
  * The XFree GLINT driver will (I think to implement hardware cursor
@@ -73,8 +73,8 @@ static char *mode __initdata = NULL;
  * these flags allow the user to specify that requests for +ve sync
  * should be silently turned in -ve sync.
  */
-static int lowhsync __initdata = 0;
-static int lowvsync __initdata = 0;	
+static int lowhsync __devinitdata = 0;
+static int lowvsync __devinitdata = 0;	
 
 /*
  * The hardware state of the graphics card that isn't part of the
@@ -97,7 +97,7 @@ struct pm2fb_par
  * Here we define the default structs fb_fix_screeninfo and fb_var_screeninfo
  * if we don't use modedb.
  */
-static struct fb_fix_screeninfo pm2fb_fix __initdata = {
+static struct fb_fix_screeninfo pm2fb_fix __devinitdata = {
 	.id =		"", 
 	.type =		FB_TYPE_PACKED_PIXELS,
 	.visual =	FB_VISUAL_PSEUDOCOLOR,
@@ -110,7 +110,7 @@ static struct fb_fix_screeninfo pm2fb_fi
 /*
  * Default video mode. In case the modedb doesn't work.
  */
-static struct fb_var_screeninfo pm2fb_var __initdata = {
+static struct fb_var_screeninfo pm2fb_var __devinitdata = {
 	/* "640x480, 8 bpp @ 60 Hz */
 	.xres =		640,
 	.yres =		480,


-------------------------------------------------------
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

  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 ` [PATCH 1/11] asiliantfb: " Randy.Dunlap
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 ` Randy.Dunlap [this message]
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=20050309101915.6d7b7ea6.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).