linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Paul Mackerras <paulus@samba.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the kvm-ppc tree
Date: Wed, 16 May 2012 11:19:35 +0200	[thread overview]
Message-ID: <4FB37127.8070507@suse.de> (raw)
In-Reply-To: <20120516091501.GA30694@bloggs.ozlabs.ibm.com>

On 05/16/2012 11:15 AM, Paul Mackerras wrote:
> On Wed, May 16, 2012 at 05:24:16PM +1000, Stephen Rothwell wrote:
>> Hi Alexander,
>>
>> After merging the kvm-ppc tree, today's linux-next build (powerpc
>> ppc64_defconfig) failed like this:
>>
>> ERROR: "kvm_hpt_order" [arch/powerpc/kvm/kvm.ko] undefined!
>>
>> Caused by commit ec26346431bb ("KVM: PPC: Book3S HV: Make the guest hash
>> table size configurable").
> Oops, my fault, kvm_hpt_order needs to be exported for when KVM is
> a module.  Patch coming.

Fixed in kvm-ppc-next. Sorry for the noise.


Alex

  reply	other threads:[~2012-05-16  9:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16  7:24 linux-next: build failure after merge of the kvm-ppc tree Stephen Rothwell
2012-05-16  9:15 ` Paul Mackerras
2012-05-16  9:19   ` Alexander Graf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-04-28  4:31 Stephen Rothwell
2017-04-07  6:37 Stephen Rothwell
2014-08-04 10:36 Stephen Rothwell
2014-08-05  9:19 ` Paolo Bonzini
2012-10-15  0:41 Stephen Rothwell
2012-07-05  5:49 Stephen Rothwell
2012-07-05  6:02 ` Alexander Graf
2012-07-05 14:20   ` Yoder Stuart-B08248
2012-05-01  3:55 Stephen Rothwell
2012-05-01  4:55 ` Benjamin Herrenschmidt
2012-05-01  8:37   ` Alexander Graf
2012-05-02 13:16 ` Alexander Graf

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=4FB37127.8070507@suse.de \
    --to=agraf@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=sfr@canb.auug.org.au \
    /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).