From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problem with using spinlocks when kernel is compiled without smp-support
Date: Thu, 08 Dec 2005 22:24:58 -0600 [thread overview]
Message-ID: <4399071A.10308@shaw.ca> (raw)
In-Reply-To: <5hwF1-kN-17@gated-at.bofh.it>
Dirk Henning Gerdes wrote:
> Hello Andrew!
>
> I have the following problem on 2.6.15-rc5-mm1
>
> When compiling a module using spinlocks I get the following
> error-message, when SMP is disabled in my Kernel-config:
..
> shouldn't it be possible to use spinlocks in my code even if I don't
> support SMP for compatiblity ?
Yes, it is, something must be set up wrong in your compilation. In
particular, are you trying to use old 2.4-style makefiles to build
instead of one that calls the kernel's build system? If so, don't, it
doesn't work..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2005-12-09 4:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5hwF1-kN-17@gated-at.bofh.it>
2005-12-09 4:24 ` Robert Hancock [this message]
2005-12-08 16:10 Problem with using spinlocks when kernel is compiled without smp-support Dirk Henning Gerdes
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=4399071A.10308@shaw.ca \
--to=hancockr@shaw.ca \
--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