From: Tommy Reynolds <reynolds@redhat.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: seq_open, et. al. are not exported for modules
Date: Thu, 29 Nov 2001 14:08:35 -0600 [thread overview]
Message-ID: <20011129140835.26e8e40e.reynolds@redhat.com> (raw)
In-Reply-To: <20011129133911.4816fe2b.reynolds@redhat.com>
In-Reply-To: <20011129133911.4816fe2b.reynolds@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
More important activities lacking, "Tommy Reynolds" <reynolds@redhat.com> wrote:
> Alex,
>
> The patch below, relative to 2.4.16, exports the seq_FOO symbols so they can be
> used from a loadable kernel module.
The patch omitted "seq_printf" ;-(
This one doesn't:
--- linux/kernel/ksyms.c.orig Thu Nov 29 13:14:10 2001
+++ linux/kernel/ksyms.c Thu Nov 29 13:58:27 2001
@@ -46,6 +46,7 @@
#include <linux/tty.h>
#include <linux/in6.h>
#include <linux/completion.h>
+#include <linux/seq_file.h>
#include <asm/checksum.h>
#if defined(CONFIG_PROC_FS)
@@ -559,3 +560,12 @@ EXPORT_SYMBOL(init_task_union);
EXPORT_SYMBOL(tasklist_lock);
EXPORT_SYMBOL(pidhash);
+
+/* Sequential file systems */
+
+EXPORT_SYMBOL(seq_open);
+EXPORT_SYMBOL(seq_read);
+EXPORT_SYMBOL(seq_lseek);
+EXPORT_SYMBOL(seq_release);
+EXPORT_SYMBOL(seq_escape);
+EXPORT_SYMBOL(seq_printf);
---------------------------------------------+-----------------------------
Tommy Reynolds | mailto: <reynolds@redhat.com>
Red Hat, Inc., Embedded Development Services | Phone: +1.256.704.9286
307 Wynn Drive NW, Huntsville, AL 35805 USA | FAX: +1.256.837.3839
Senior Software Developer | Mobile: +1.919.641.2923
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2001-11-29 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 19:39 Tommy Reynolds
2001-11-29 20:08 ` Tommy Reynolds [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=20011129140835.26e8e40e.reynolds@redhat.com \
--to=reynolds@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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
all inboxes | Powered by JetHome®