All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-ppc <qemu-ppc@nongnu.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] PPC: KVM: Compile fix for qemu_notify_event
Date: Thu, 29 Aug 2013 11:02:28 +0200	[thread overview]
Message-ID: <521F0E24.80009@suse.de> (raw)
In-Reply-To: <1377735229-54669-1-git-send-email-agraf@suse.de>

Am 29.08.2013 02:13, schrieb Alexander Graf:
> The function qemu_notify_event is defined by a header that we don't
> include in the PPC KVM code. Include it to get the code building
> again.
> 
>   target-ppc/kvm_ppc.c: In function 'kvmppc_timer_hack':
>   target-ppc/kvm_ppc.c:26:5: error: implicit declaration of function 'qemu_notify_event' [-Werror=implicit-function-declaration]
>   target-ppc/kvm_ppc.c:26:5: error: nested extern declaration of 'qemu_notify_event' [-Werror=nested-externs]
> 
> Signed-off-by: Alexander Graf <agraf@suse.de>
> ---
>  target-ppc/kvm_ppc.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/target-ppc/kvm_ppc.c b/target-ppc/kvm_ppc.c
> index 9b83655..f769acd 100644
> --- a/target-ppc/kvm_ppc.c
> +++ b/target-ppc/kvm_ppc.c
> @@ -15,6 +15,7 @@
>  #include "qemu/timer.h"
>  #include "kvm_ppc.h"
>  #include "sysemu/device_tree.h"
> +#include "qemu/main-loop.h"
>  
>  #define PROC_DEVTREE_PATH "/proc/device-tree"
>  

Matches my local fix, so

Tested-by: Andreas Färber <afaerber@suse.de>

but I didn't find out yet who/what broke this, since the
qemu_notify_event() line hasn't changed in a long time according to
git-blame...

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

      reply	other threads:[~2013-08-29  9:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29  0:13 [Qemu-devel] [PATCH] PPC: KVM: Compile fix for qemu_notify_event Alexander Graf
2013-08-29  9:02 ` Andreas Färber [this message]

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=521F0E24.80009@suse.de \
    --to=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.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 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.