Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Linus <torvalds@linux-foundation.org>
Subject: linux-next:  Linus' tree build failure
Date: Mon, 9 Feb 2009 19:29:58 +1100	[thread overview]
Message-ID: <20090209192958.f7dc3b92.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 956 bytes --]

Hi Chris,

Today's linux-next build (powerpc allyesconfig) failed like this:

fs/btrfs/locking.c: In function 'btrfs_path_lock_waiting':
fs/btrfs/locking.c:254: error: implicit declaration of function '__raw_spin_is_contended'

CONFIG_PREEMPT is not set (since CONFIG_PREEMPT_NONE takes precedence
over it) which means that CONFIG_GENERIC_LOCKBREAK is not set (since it
depends on CONFIG_PREEMPT - at least on powerpc). So spin_is_contended()
is __raw_spin_is_contended().

__raw_spin_is_contended is only defined for UP, MIPS and X86.

Commit b4ce94de9b4d64e8ab3cf155d13653c666e22b9b ("Btrfs: Change btree
locking to use explicit blocking points") from Linus' tree added the
first generic non CONFIG_PREEMPT usage via a call to spin_is_contended().

I got past this for today by building the PowerPC allyesconfig without
btrfs.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

                 reply	other threads:[~2009-02-09  8:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20090209192958.f7dc3b92.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=chris.mason@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=torvalds@linux-foundation.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