All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Stefan Weil <sw@weilnetz.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-barrier: Fix compilation on i386 hosts
Date: Sat, 6 Oct 2012 20:35:25 +0200	[thread overview]
Message-ID: <20121006183525.GA31647@ohm.aurel32.net> (raw)
In-Reply-To: <1349520375-9853-1-git-send-email-sw@weilnetz.de>

On Sat, Oct 06, 2012 at 12:46:15PM +0200, Stefan Weil wrote:
> Commit 610b823ef66b993660f1ab1447a769f190e4f3b3 uses QEMU_GNUC_PREREQ
> on i386 hosts.
> 
> That macro is defined in qemu-common.h which is not always included
> before qemu-barrier.h, so compilation on i386 hosts was broken.
> 
> Signed-off-by: Stefan Weil <sw@weilnetz.de>
> ---
> 
> This patch fixes broken compilation for i386 hosts which
> was reported by the buildbot:
> 
> http://buildbot.b1-systems.de/qemu/builders/default_mingw32/builds/396
> 
> Regards
> 
> Stefan Weil
> 
>  qemu-barrier.h |    2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/qemu-barrier.h b/qemu-barrier.h
> index 16f0942..1de914e 100644
> --- a/qemu-barrier.h
> +++ b/qemu-barrier.h
> @@ -6,6 +6,8 @@
>  
>  #if defined(__i386__)
>  
> +#include "qemu-common.h"        /* QEMU_GNUC_PREREQ */
> +
>  /*
>   * Because of the strongly ordered x86 storage model, wmb() and rmb() are nops
>   * on x86(well, a compiler barrier only).  Well, at least as long as
> -- 
> 1.7.10
> 

Thanks, applied.

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

  reply	other threads:[~2012-10-06 18:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-06 10:46 [Qemu-devel] [PATCH] qemu-barrier: Fix compilation on i386 hosts Stefan Weil
2012-10-06 18:35 ` Aurelien Jarno [this message]
2012-10-07 16:10 ` Blue Swirl
2012-10-07 18:10   ` Aurelien Jarno

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=20121006183525.GA31647@ohm.aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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.