linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alexander Graf <agraf@suse.de>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build failure after merge of the kvm-ppc tree
Date: Mon, 15 Oct 2012 11:41:29 +1100	[thread overview]
Message-ID: <20121015114129.c5be2be04e44043682b6b661@canb.auug.org.au> (raw)

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

Hi Alexander,

Take into account that I removed the top two WIP commits from the kvm-ppc
tree before the following ...

After merging the kvm-ppc tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:

ERROR: ".kvm_irqfd" [arch/powerpc/kvm/kvm.ko] undefined!
ERROR: ".kvm_irqfd_release" [arch/powerpc/kvm/kvm.ko] undefined!
ERROR: ".kvm_eventfd_init" [arch/powerpc/kvm/kvm.ko] undefined!
ERROR: ".kvm_ioeventfd" [arch/powerpc/kvm/kvm.ko] undefined!

I have used the kvm-ppc tree from next-20121012 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2012-10-15  0:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15  0:41 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-04-28  4:31 linux-next: build failure after merge of the kvm-ppc tree Stephen Rothwell
2017-04-07  6:37 Stephen Rothwell
2014-08-04 10:36 Stephen Rothwell
2014-08-05  9:19 ` Paolo Bonzini
2012-07-05  5:49 Stephen Rothwell
2012-07-05  6:02 ` Alexander Graf
2012-07-05 14:20   ` Yoder Stuart-B08248
2012-05-16  7:24 Stephen Rothwell
2012-05-16  9:15 ` Paul Mackerras
2012-05-16  9:19   ` Alexander Graf
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=20121015114129.c5be2be04e44043682b6b661@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=agraf@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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).