public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Paul Mundt <lethal@linux-sh•org>
Cc: linux-next@vger•kernel.org,
	Mathieu Desnoyers <mathieu.desnoyers@polymtl•ca>,
	Thomas Gleixner <tglx@linutronix•de>, Ingo Molnar <mingo@elte•hu>,
	"H. Peter Anvin" <hpa@zytor•com>
Subject: linux-next: sh build failure
Date: Fri, 20 Mar 2009 11:06:02 +1100	[thread overview]
Message-ID: <20090320110602.86351a91.sfr@canb.auug.org.au> (raw)

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

Hi Paul,

Yesterday's linux-next build of sh allmodconfig failed like this:

kernel/built-in.o: In function `disable_all_kprobes':
kernel/kprobes.c:1382: undefined reference to `text_mutex'
kernel/built-in.o: In function `__unregister_kprobe_top':
kernel/kprobes.c:773: undefined reference to `text_mutex'
kernel/built-in.o: In function `register_kprobe':
kernel/kprobes.c:724: undefined reference to `text_mutex'

Introduced by commit 4460fdad85becd569f11501ad5b91814814335ff ("tracing,
Text Edit Lock - kprobes architecture independent support") from the
tracing tree.  text_mutex is defined in mm/memory.c which is only built
if CONFIG_MMU is defined, which is not true for sh allmodconfig.
-- 
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-03-20  0:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-20  0:06 Stephen Rothwell [this message]
2009-03-20 18:24 ` linux-next: sh build failure Mathieu Desnoyers
2009-03-20 18:34   ` Ingo Molnar

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=20090320110602.86351a91.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=hpa@zytor$(echo .)com \
    --cc=lethal@linux-sh$(echo .)org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mathieu.desnoyers@polymtl$(echo .)ca \
    --cc=mingo@elte$(echo .)hu \
    --cc=tglx@linutronix$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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