[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <DB60B93C-DFAC-4D99-8E3C-364DAF433A07@suse.de>
Date: Wed, 28 Apr 2010 10:41:38 +0100
From: Alexander Graf <agraf@...e.de>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Avi Kivity <avi@...ranet.com>,
Marcelo Tosatti <mtosatti@...hat.com>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the final tree
Am 27.04.2010 um 06:49 schrieb Stephen Rothwell <sfr@...b.auug.org.au>:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> arch/powerpc/kvm/book3s.c: In function 'kvmppc_core_vcpu_create':
> arch/powerpc/kvm/book3s.c:1241: error: implicit declaration of
> function 'kzalloc'
> arch/powerpc/kvm/book3s.c:1241: warning: cast to pointer from
> integer of different size
> arch/powerpc/kvm/book3s.c:1281: error: implicit declaration of
> function 'kfree'
>
> Caused by commit 046cdc052ffcbf1ee1c627ef811031d18654bafe ("KVM: PPC:
> Improve indirect svcpu accessors") from the kvm tree.
>
> You have to include slab.h directly to use kzalloc/kfree ...
>
> I have applied the following patch for today.
Thank you. Is that behavior new? I didn't get any breakage when
compile testing myself.
Will this commit automatically move back to kvm.git or is there any
intervention required from my side?
Alex
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists