Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@enix.org>
To: linux-mips@linux-mips.org
Cc: mentre@tcl.ite.mee.com
Subject: Compilation fails with CONFIG_DEBUG_SPINLOCK
Date: Wed, 13 Oct 2004 11:20:57 +0200	[thread overview]
Message-ID: <20041013092057.GQ11236@enix.org> (raw)

Hello,

With the last CVS, if you check CONFIG_DEBUG_SPINLOCK, the compilation
fails :

arch/mips/kernel/built-in.o(.text+0x2e84): In function `probe_irq_on':
: undefined reference to `atomic_lock'
arch/mips/kernel/built-in.o(.text+0x2e88): In function `probe_irq_on':
: undefined reference to `atomic_lock'
arch/mips/kernel/built-in.o(.text+0x2e90): In function `probe_irq_on':
: undefined reference to `atomic_lock'
arch/mips/kernel/built-in.o(.text+0x2e94): In function `probe_irq_on':
: undefined reference to `atomic_lock'
arch/mips/kernel/built-in.o(.text+0x2ebc): In function `probe_irq_on':
: undefined reference to `atomic_lock'
arch/mips/kernel/built-in.o(.text+0x2ec0): more undefined references
to `atomic_lock' follow
make: *** [.tmp_vmlinux1] Error 1

Some macros in include/asm/atomic.h uses a spinlock called
atomic_lock. An "extern" definition is made at the top of the file,
but the real spinlock is not defined anywhere.

I think this is trivial to fix, but I'm not sure what is the right
place to declare the spin lock and to initialize it.

Thomas
-- 
PETAZZONI Thomas - thomas.petazzoni@enix.org 
http://thomas.enix.org - Jabber: kos_tom@sourcecode.de
KOS: http://kos.enix.org/ - Lolut: http://lolut.utbm.info
Fingerprint : 0BE1 4CF3 CEA4 AC9D CC6E  1624 F653 CB30 98D3 F7A7

             reply	other threads:[~2004-10-13  9:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-13  9:20 Thomas Petazzoni [this message]
2004-10-18 10:03 ` Compilation fails with CONFIG_DEBUG_SPINLOCK Thomas Petazzoni
2004-10-22 12:50 ` Ralf Baechle

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=20041013092057.GQ11236@enix.org \
    --to=thomas.petazzoni@enix.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mentre@tcl.ite.mee.com \
    /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