linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: ajoshi@shell.unixbox.com,
	linux-fbdev-devel@lists.sourceforge.net, adaplas@pol.net
Subject: [PATCH] radeonfb: fix init/exit section usage
Date: Fri, 07 Jan 2005 11:28:07 -0800	[thread overview]
Message-ID: <41DEE2C7.4030200@osdl.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 521 bytes --]


Fix 3 instances of calling exit section function from text or init:
Error: ./drivers/video/aty/radeon_base.o .text refers to 000029e5 
R_386_PC32        .exit.text
Error: ./drivers/video/aty/radeon_base.o .text refers to 00002a60 
R_386_PC32        .exit.text
Error: ./drivers/video/aty/radeon_base.o .init.text refers to 00000192 
R_386_PC32        .exit.text

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

diffstat:=
  drivers/video/aty/radeon_base.c |    2 +-
  1 files changed, 1 insertion(+), 1 deletion(-)

---

[-- Attachment #2: radeonfb_init_exit.patch --]
[-- Type: text/x-patch, Size: 566 bytes --]


diff -Naurp ./drivers/video/aty/radeon_base.c~radeonfb_initexit ./drivers/video/aty/radeon_base.c
--- ./drivers/video/aty/radeon_base.c~radeonfb_initexit	2005-01-06 21:18:20.920585008 -0800
+++ ./drivers/video/aty/radeon_base.c	2005-01-07 10:30:16.661094480 -0800
@@ -261,7 +261,7 @@ static struct backlight_controller radeo
 
 #endif /* CONFIG_PPC_OF */
 
-static void __devexit radeon_unmap_ROM(struct radeonfb_info *rinfo, struct pci_dev *dev)
+static void radeon_unmap_ROM(struct radeonfb_info *rinfo, struct pci_dev *dev)
 {
 	if (!rinfo->bios_seg)
 		return;

             reply	other threads:[~2005-01-07 20:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-07 19:28 Randy.Dunlap [this message]
2005-01-07 21:54 ` [PATCH] radeonfb: fix init/exit section usage Kronos
2005-01-07 21:24   ` 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=41DEE2C7.4030200@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=adaplas@pol.net \
    --cc=ajoshi@shell.unixbox.com \
    --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).