From: malware@t-online.de (Michael Mueller)
To: alan@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] Using I2O modules with I2O core in kernel
Date: Tue, 13 Mar 2001 07:56:34 +0100 [thread overview]
Message-ID: <200103130656.HAA27068@fire.malware.de> (raw)
Hi Alan and folks,
I got asked why it gives unresolved symbols (and how to fix it) for the
I2O modules. During the session I noticed this is due to the fact the
I2O core is built into the kernel but the other I2O support built as
module. So the quick hack to resolv that problem was adding the missing
symbols into ksyms.c.
Later on I noticed its possible to avoid this hacking simple by doing
the EXPORT_SYMBOL within the original source module. This was only done
for the case it would have been compiled as kernel module. The patch is
appended.
Michael
reply other threads:[~2001-03-13 6:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200103130656.HAA27068@fire.malware.de \
--to=malware@t-online.de \
--cc=alan@redhat.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