From: Ralf Baechle <ralf@linux-mips.org>
To: xavier prabhu <xavier_prabhu@linuxmail.org>
Cc: linux-mips@linux-mips.org
Subject: Re: __up and __down not found in 2.25 kernel
Date: Thu, 25 Mar 2004 10:01:28 +0100 [thread overview]
Message-ID: <20040325090128.GA27145@linux-mips.org> (raw)
In-Reply-To: <20040325083629.8255C39834A@ws5-1.us4.outblaze.com>
On Thu, Mar 25, 2004 at 04:36:29PM +0800, xavier prabhu wrote:
> I'm using a module which is developed for 2.22 kernel.
> This module uses __up and __down semaphore functions.
> While I insmod this module with 2.25 kernel,
> I get the following error message
> "insmod: unresolved symbol __up
> insmod: unresolved symbol __down"
>
> I checked the semaphore.c. It doesn't define these two functions.
> Is there any way to work around this issue.
Sounds like you're using some broken tree - get the sources from cvs.
Ralf
next prev parent reply other threads:[~2004-03-25 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 8:36 __up and __down not found in 2.25 kernel xavier prabhu
2004-03-25 9:01 ` Ralf Baechle [this message]
2004-03-25 10:18 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2004-03-25 9:51 xavier prabhu
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=20040325090128.GA27145@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=xavier_prabhu@linuxmail.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