From: Nico Schottelius <nicos@pcsystems.de>
To: Erik Mouw <J.A.K.Mouw@ITS.TUDelft.NL>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: unresolved symbols printk ?
Date: Tue, 29 May 2001 15:54:36 +0200 [thread overview]
Message-ID: <3B13AA1C.AF1F86F9@pcsystems.de> (raw)
In-Reply-To: <3B128437.7C166E53@pcsystems.de> <20010528214437.A9384@arthur.ubicom.tudelft.nl>
> On Mon, May 28, 2001 at 07:00:39PM +0200, Nico Schottelius wrote:
> > I am having problems with loading modules:
> > I always get the unresolved symbols message.
> > I didn't find any documentation for that, can you help me ?
>
> You did read question 8.8 from the linux-kernel mailing list FAQ?
>
> http://www.tux.org/lkml/#s8-8
Right now, yes :)
Just a small question, what could be the reason I have a broken
Makefile ?
This seems to happen frequently, if there is a need
to name it into the lkml. I am surprised
a makefile gets screwed up ?
Nico
next prev parent reply other threads:[~2001-05-29 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-28 17:00 unresolved symbols printk ? Nico Schottelius
2001-05-28 19:44 ` Erik Mouw
2001-05-29 13:54 ` Nico Schottelius [this message]
2001-05-29 14:55 ` Keith Owens
2001-05-30 12:36 ` Nico Schottelius
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=3B13AA1C.AF1F86F9@pcsystems.de \
--to=nicos@pcsystems.de \
--cc=J.A.K.Mouw@ITS.TUDelft.NL \
--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