From: "David S. Miller" <davem@davemloft.net>
To: "O.Sezer" <sezeroz@ttnet.net.tr>
Cc: linux-kernel@vger.kernel.org, bunk@stusta.de
Subject: Re: [patch] 2.4.28-rc3: neigh_for_each must be EXPORT_SYMBOL'ed
Date: Mon, 15 Nov 2004 15:17:32 -0800 [thread overview]
Message-ID: <20041115151732.4f26c139.davem@davemloft.net> (raw)
In-Reply-To: <4198CAFC.7030705@ttnet.net.tr>
On Mon, 15 Nov 2004 17:27:56 +0200
"O.Sezer" <sezeroz@ttnet.net.tr> 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
Good catch, I've fixed this in my tree and will push
upstream.
next prev parent reply other threads:[~2004-11-15 23:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 15:27 O.Sezer
2004-11-15 23:17 ` David S. Miller [this message]
2004-11-15 23:18 ` [patch] 2.4.28-rc3: __neigh_for_each_release " Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2004-11-12 18:00 Linux 2.4.28-rc3 Marcelo Tosatti
2004-11-13 20:07 ` [patch] 2.4.28-rc3: neigh_for_each must be EXPORT_SYMBOL'ed Adrian Bunk
2004-11-14 7:25 ` David S. Miller
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=20041115151732.4f26c139.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bunk@stusta.de \
--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
Powered by JetHome