public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: "André Dahlqvist" <andre.dahlqvist@telia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Sound fails to build when non-modular with new binutils
Date: Fri, 28 Dec 2001 10:29:07 -0800	[thread overview]
Message-ID: <3C2CB9F3.DC25E959@zip.com.au> (raw)
In-Reply-To: <20011228151608.GA1870@telia.com> <4841.1009556591@ocs3.intra.ocs.com.au>, <4841.1009556591@ocs3.intra.ocs.com.au> <20011228170349.GA4955@telia.com>

André Dahlqvist wrote:
> 
> Keith Owens <kaos@ocs.com.au> wrote:
> 
> > Run this, it will say precisely where the problem lies:
> 
> Thanks Keith. Below is the output:
> 
> Finding objects, 315 objects, ignoring 0 module(s)
> Finding conglomerates, ignoring 29 conglomerate(s)
> Scanning objects
> Error: ./drivers/sound/via82cxxx_audio.o .data refers to 00000034
> R_386_32          .text.exit
> Done

Could you please check that this works OK?

--- linux-2.4.18-pre1/drivers/sound/via82cxxx_audio.c	Fri Dec 21 11:19:13 2001
+++ linux-akpm/drivers/sound/via82cxxx_audio.c	Fri Dec 28 10:27:51 2001
@@ -365,7 +365,7 @@ static struct pci_driver via_driver = {
 	name:		VIA_MODULE_NAME,
 	id_table:	via_pci_tbl,
 	probe:		via_init_one,
-	remove:		via_remove_one,
+	remove:		__devexit_p(via_remove_one),
 };
 
 
@@ -3271,7 +3271,7 @@ err_out:
 }
 
 
-static void __exit via_remove_one (struct pci_dev *pdev)
+static void __devexit via_remove_one (struct pci_dev *pdev)
 {
 	struct via_info *card;

  reply	other threads:[~2001-12-28 18:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-28 15:16 Sound fails to build when non-modular with new binutils André Dahlqvist
2001-12-28 16:23 ` Keith Owens
2001-12-28 17:03   ` André Dahlqvist
2001-12-28 18:29     ` Andrew Morton [this message]
2001-12-29  0:11       ` André Dahlqvist

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=3C2CB9F3.DC25E959@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=andre.dahlqvist@telia.com \
    --cc=linux-kernel@vger.kernel.org \
    /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