From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Marcelo Tosatti <mtosatti@redhat.com>, Avi Kivity <avi@redhat.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Eric B Munson <emunson@mgebm.net>, Alexander Graf <agraf@suse.de>
Subject: Re: linux-next: build failure after merge of the final tree (kvm-ppc tree related)
Date: Fri, 20 Apr 2012 10:10:12 +1000 [thread overview]
Message-ID: <20120420101012.591b5e64a8939135bf5cd167@canb.auug.org.au> (raw)
In-Reply-To: <20120419163535.52c99a34e2664063d654ac4d@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
Hi all,
On Thu, 19 Apr 2012 16:35:35 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the final tree, today's linux-next build (sparc64 defconfig)
> failed like this:
>
> In file included from kernel/watchdog.c:27:0:
> include/linux/kvm_para.h: In function 'kvm_para_has_feature':
> include/linux/kvm_para.h:32:2: error: implicit declaration of function 'kvm_arch_para_features' [-Werror=implicit-function-declaration]
>
> Caused by commit 5d1c0f4a80a6 ("watchdog: add check for suspended vm in
> softlockup detector"). This build has no KVM related CONFIG options set.
>
> I have reverted that commit for today.
This build failure now belongs to the kvm tree ...
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-04-20 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 6:35 linux-next: build failure after merge of the final tree (kvm-ppc tree related) Stephen Rothwell
2012-04-20 0:10 ` Stephen Rothwell [this message]
2012-04-20 1:14 ` Marcelo Tosatti
2012-04-20 3:35 ` Stephen Rothwell
2012-04-27 5:54 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=20120420101012.591b5e64a8939135bf5cd167@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=emunson@mgebm.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mtosatti@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.