From: Adrian Bunk <bunk@stusta.de>
To: "O.Sezer" <sezeroz@ttnet.net.tr>
Cc: linux-kernel@vger.kernel.org, davem@davemloft.net
Subject: [patch] 2.4.28-rc3: __neigh_for_each_release must be EXPORT_SYMBOL'ed
Date: Tue, 16 Nov 2004 00:18:48 +0100 [thread overview]
Message-ID: <20041115231848.GB4946@stusta.de> (raw)
In-Reply-To: <4198CAFC.7030705@ttnet.net.tr>
On Mon, Nov 15, 2004 at 05:27:56PM +0200, O.Sezer wrote:
> A similar export should also be needed for __neigh_for_each_release :
>
> /sbin/depmod -ae -F System.map 2.4.28-rc3aac2
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.28-rc3aac2/kernel/net/atm/clip.o
> depmod: __neigh_for_each_release
Thanks for this report.
For some strange reason, this wasn't covered by the modular .config I
used for testing...
Patch (on top of my other patch) below.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.4.28-rc3-modular/net/core/neighbour.c.old 2004-11-15 22:14:54.000000000 +0100
+++ linux-2.4.28-rc3-modular/net/core/neighbour.c 2004-11-15 22:15:19.000000000 +0100
@@ -1597,6 +1597,7 @@
}
}
}
+EXPORT_SYMBOL(__neigh_for_each_release);
#ifdef CONFIG_PROC_FS
prev parent reply other threads:[~2004-11-15 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 15:27 [patch] 2.4.28-rc3: neigh_for_each must be EXPORT_SYMBOL'ed O.Sezer
2004-11-15 23:17 ` David S. Miller
2004-11-15 23:18 ` Adrian Bunk [this message]
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=20041115231848.GB4946@stusta.de \
--to=bunk@stusta.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sezeroz@ttnet.net.tr \
/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