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


Fix radeonfb section references by changing __initdata
  to __devinitdata.

Error: ./drivers/video/radeonfb.o .text refers to 0000000000002037 R_X86_64_PC32     .init.data+0x0000000000000003
Error: ./drivers/video/radeonfb.o .text refers to 0000000000002491 R_X86_64_PC32     .init.data
Error: ./drivers/video/radeonfb.o .text refers to 0000000000002870 R_X86_64_PC32     .init.data+0x000000000000000c
Error: ./drivers/video/radeonfb.o .text refers to 0000000000002a21 R_X86_64_PC32     .init.data+0xfffffffffffffffb

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

diffstat:=
 drivers/video/radeonfb.c |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff -Naurp ./drivers/video/radeonfb.c~video_radfb_sections ./drivers/video/radeonfb.c
--- ./drivers/video/radeonfb.c~video_radfb_sections	2005-03-01 23:38:32.000000000 -0800
+++ ./drivers/video/radeonfb.c	2005-03-08 15:12:05.000000000 -0800
@@ -658,13 +658,13 @@ static __inline__ int _max(int val1, int
  * globals
  */
         
-static char *mode_option __initdata;
+static char *mode_option;
 static char noaccel = 0;
 static char mirror = 0;
-static int panel_yres __initdata = 0;
-static char force_dfp __initdata = 0;
+static int panel_yres = 0;
+static char force_dfp = 0;
 static struct radeonfb_info *board_list = NULL;
-static char nomtrr __initdata = 0;
+static char nomtrr = 0;
 
 /*
  * prototypes


-------------------------------------------------------
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 ` [PATCH 6/11] pm2fb: " Randy.Dunlap
2005-03-09 18:23 ` Randy.Dunlap [this message]
2005-03-09 18:35   ` [PATCH 7/11] radeonfb: " 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=20050309102315.0c181db7.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).