public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: Link error with linux-2.5 bk
Date: Wed, 21 Jan 2004 17:20:19 +0000	[thread overview]
Message-ID: <20040121182019.358eed82.ak@suse.de> (raw)
In-Reply-To: <20040120144809.GT27591@localhost>

On Wed, 21 Jan 2004 08:55:19 -0800
"Luck, Tony" <tony.luck@intel.com> wrote:

> >   LD      .tmp_vmlinux1
> > local symbol 0: discarded in section `.exit.text' from drivers/built-in.o
> 
> My money is on this change to drivers/net/dummy.c (clipped from diff
> between bk3 and bk4 trees).  "dummy_free_one()" is marked as __exit (so
> we'll try to discard it), but it is called by dummy_init_module().
> 
> Dropping the "__exit" will fix it (but there may be other fixes).  Copying
> Andi Kleen, as according to BitKeeper he appears to be the author of this
> change.

Yep, the __exit is wrong. Thanks, Tony.

Jeff, can you apply this patch, please? It should fix compiling in of the dummy
device. 

Thanks.

-Andi

--- linux-2.6.2rc1-amd64/drivers/net/dummy.c-o	2004-01-21 15:52:42.000000000 +0100
+++ linux-2.6.2rc1-amd64/drivers/net/dummy.c	2004-01-21 18:19:05.000000000 +0100
@@ -112,7 +112,7 @@
 	return err;
 }
 
-static void __exit dummy_free_one(int index) 
+static void dummy_free_one(int index) 
 {
 	unregister_netdev(dummies[index]);
 	free_netdev(dummies[index]);



  parent reply	other threads:[~2004-01-21 17:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-20 14:48 Link error with linux-2.5 bk Martin Hicks
2004-01-20 21:09 ` Darren Williams
2004-01-21 16:55 ` Luck, Tony
2004-01-21 17:20 ` Andi Kleen [this message]
2004-01-21 17:42 ` David Mosberger
2004-01-21 17:57 ` Randy.Dunlap
2004-01-21 17:57 ` Luck, Tony
2004-01-21 18:01 ` David Mosberger
2004-01-21 18:11 ` Andi Kleen

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=20040121182019.358eed82.ak@suse.de \
    --to=ak@suse.de \
    --cc=linux-ia64@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