From: Samuel Rydh <samuel@ibrium.se>
To: linuxppc-dev@lists.linuxppc.org
Subject: Versioned module symbols broken for PPC?
Date: Sat, 4 Aug 2001 15:38:49 +0200 [thread overview]
Message-ID: <20010804153849.A2056@ibrium.se> (raw)
The support for versioned symbols seems to be broken.
After a mrproper recompile, /proc/ksyms contains entries
like
c0148940 nf_hook_slow_R__ver_nf_hook_slow
which obviously is wrong. (This is with Ben's tree,
but I've seen it in the BK tree too. I think
this problem appeared in 2.4.5-something).
/Samuel
----------------------------------------------------------
E-mail <samuel@ibrium.se> WWW: <http://www.ibrium.se>
Phone/fax: (home) +46 8 4418431, (work) +46 8 790nnnn
----------------------------------------------------------
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-08-04 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-04 13:38 Samuel Rydh [this message]
2001-08-04 14:37 ` Versioned module symbols broken for PPC? Samuel Rydh
2001-08-04 16:07 ` Tom Rini
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=20010804153849.A2056@ibrium.se \
--to=samuel@ibrium.se \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).