All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert Cranford <ac9410@bellsouth.net>
To: ollie@sis.com.tw, linux-kernel@vger.kernel.org
Subject: [PATCH] 2.4.18-pre1 sound/trident fix with newer binutils
Date: Wed, 02 Jan 2002 07:46:12 -0500	[thread overview]
Message-ID: <3C330114.D4F66B45@bellsouth.net> (raw)

Hello Ollie,
Small problem.
I cannot build kernel with binutils-2.11.92.0.12.3

Using ARCH='i386' AS='as' LD='ld' CC='/usr/bin/gcc' CPP='/usr/bin/gcc -E' AR='ar' HOSTAS='as' HOSTLD='gcc' HOSTCC='gcc' HOSTAR='ar'
drivers/sound/trident.o(.data+0x154): undefined reference to `local symbols in discarded section .text.exit'

Please submit the attached patch to Marcelo and Linus
for 2.4 and 2.5 respectfully.  This patch also works
with older binutils-2.11.2
Thanks,
Albert
--- linux-2.4.18-pre1/drivers/sound/trident.c.orig      Mon Dec 31 16:32:25 2001
+++ linux/drivers/sound/trident.c       Mon Dec 31 16:32:44 2001
@@ -4141,7 +4141,7 @@
        goto out;
 }
 
-static void __exit trident_remove(struct pci_dev *pci_dev)
+static void __devexit trident_remove(struct pci_dev *pci_dev)
 {
        int i;
        struct trident_card *card = pci_get_drvdata(pci_dev);
@@ -4194,7 +4194,9 @@
        name:           TRIDENT_MODULE_NAME,
        id_table:       trident_pci_tbl,
        probe:          trident_probe,
+#ifdef DEVEXIT_LINKED
        remove:         trident_remove,
+#endif
        suspend:        trident_suspend,
        resume:         trident_resume
 };
@@ -4214,7 +4216,7 @@
        return 0;
 }
 
-static void __exit trident_cleanup_module (void)
+static void __devexit trident_cleanup_module (void)
 {
        pci_unregister_driver(&trident_pci_driver);
 }


-- 
Albert Cranford Deerfield Beach FL USA
ac9410@bellsouth.net


             reply	other threads:[~2002-01-02 12:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-02 12:46 Albert Cranford [this message]
2002-01-02 13:08 ` [PATCH] 2.4.18-pre1 sound/trident fix with newer binutils Keith Owens

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=3C330114.D4F66B45@bellsouth.net \
    --to=ac9410@bellsouth.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ollie@sis.com.tw \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.