From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: Don Zickus <dzickus@redhat.com>, ppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: tip build problem on powerpc
Date: Tue, 9 Feb 2010 10:07:00 +1100 [thread overview]
Message-ID: <20100209100700.81685ffe.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
Hi all,
Last night's build of tip/master on powerpc produced these errors:
kernel/nmi_watchdog.c:33: error: redefinition of 'touch_nmi_watchdog'
kernel/nmi_watchdog.c:59: error: 'nmi_watchdog_enabled' undeclared (first use in this function)
kernel/nmi_watchdog.c:59: error: (Each undeclared identifier is reported only once
kernel/nmi_watchdog.c:59: error: for each function it appears in.)
kernel/nmi_watchdog.c:109: error: implicit declaration of function 'die_nmi'
kernel/nmi_watchdog.c:136: error: 'cpu_khz' undeclared (first use in this function)
This was from the powerpc pseries_defconfig build (as well as the
pamc32_defconfig, ppc6xx_defconfig and ppc64_defconfig builds). Caused
by commit 1fb9d6ad2766a1dd70d167552988375049a97f21 ("nmi_watchdog: Add
new, generic implementation, using perf events") but exposed by commit
84e478c6f1eb9c4bfa1fff2f8108e9a061b46428 ("nmi_watchdog: Config option to
enable new nmi_watchdog").
Full logs, configs: http://kisskb.ellerman.id.au/kisskb/branch/12/
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-02-08 23:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 23:07 Stephen Rothwell [this message]
2010-02-09 4:22 ` tip build problem on powerpc Ingo Molnar
2010-02-09 4:41 ` Stephen Rothwell
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=20100209100700.81685ffe.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dzickus@redhat.com \
--cc=hpa@zytor.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).