From: Thomas Downing <thomas.downing@ipc.com>
To: linux-kernel@vger.kernel.org
Subject: Unresolved symbol in microcode.ko - 2.5.64bk4
Date: Wed, 12 Mar 2003 12:22:22 -0500 [thread overview]
Message-ID: <200303121222.22849.thomas.downing@ipc.com> (raw)
When building microcode support for i386 PIII as a module, I get an unresolved
reference to devfs_set_file_size. Attached is a patch to fs/devfs/base.c
that fixes the problem.
Being a newbie, I don't know if that is the appropriate fix, or if devfs
should be tweeked instead.
td
---- begin patch ----
*** linux-2.5.64_o/fs/devfs/base.c Wed Mar 12 12:09:21 2003
--- linux-2.5.64/fs/devfs/base.c Wed Mar 12 12:10:18 2003
***************
*** 1953,1960 ****
--- 1953,1961 ----
EXPORT_SYMBOL(devfs_mk_symlink);
EXPORT_SYMBOL(devfs_mk_dir);
EXPORT_SYMBOL(devfs_remove);
EXPORT_SYMBOL(devfs_generate_path);
+ EXPORT_SYMBOL(devfs_set_file_size);
/**
* try_modload - Notify devfsd of an inode lookup by a non-devfsd process.
next reply other threads:[~2003-04-06 4:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 17:22 Thomas Downing [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-12 18:48 Unresolved symbol in microcode.ko - 2.5.64bk4 Downing, Thomas
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=200303121222.22849.thomas.downing@ipc.com \
--to=thomas.downing@ipc.com \
--cc=linux-kernel@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