From: Peter Williams <pwil3058@bigpond.net.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [BUG] 2.6.14-rc5-mm1 build fails for non SMP systems
Date: Tue, 25 Oct 2005 11:12:21 +1000 [thread overview]
Message-ID: <435D8675.3080303@bigpond.net.au> (raw)
Without CONFIG_DEBUG_SPINLOCK configured in I'm getting a large number
of "implicit declaration of function ‘__raw_read_unlock’" warnings and a
subsequent failure at the link stage.
A trivial change to include/linux/spinlock_up.h (i.e. moving the
definition of __raw_read_unlock() outside the ifdef) can get rid of this
warning but I'm not sure that it's the right thing to do as I suspect
this may be an indication of a less trivial problem elsewhere.
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next reply other threads:[~2005-10-25 1:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 1:12 Peter Williams [this message]
2005-10-25 1:43 ` [BUG] 2.6.14-rc5-mm1 build fails for non SMP systems Peter Williams
2005-10-25 1:51 ` Andrew Morton
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=435D8675.3080303@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=akpm@osdl.org \
--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