From: Wen Congyang <wency@cn.fujitsu.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] w32: Fix broken build (missing include file)
Date: Mon, 11 Jun 2012 09:57:56 +0800 [thread overview]
Message-ID: <4FD550A4.4030808@cn.fujitsu.com> (raw)
In-Reply-To: <1339076735-19796-1-git-send-email-sw@weilnetz.de>
At 06/07/2012 09:45 PM, Stefan Weil Wrote:
> dump.c was recently added to the code. It unconditionally
> includes sys/procfs which is not available with MinGW (w32, w64).
>
> It looks like this file is not needed at all (tested on Linux),
> so I removed it completely.
>
> Some other include statements are also redundant because they are
> already included in qemu-common, therefore they were removed, too.
>
> Signed-off-by: Stefan Weil <sw@weilnetz.de>
Thanks for your fix. It is OK to me.
Wen Congyang
> ---
>
> dump.* use GPL2 instead of GPL2+. Please fix that!
>
> Regards,
> Stefan Weil
>
>
> dump.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/dump.c b/dump.c
> index 0ca14f8..f44ce47 100644
> --- a/dump.c
> +++ b/dump.c
> @@ -12,10 +12,7 @@
> */
>
> #include "qemu-common.h"
> -#include <unistd.h>
> #include "elf.h"
> -#include <sys/procfs.h>
> -#include <glib.h>
> #include "cpu.h"
> #include "cpu-all.h"
> #include "targphys.h"
> @@ -23,7 +20,6 @@
> #include "kvm.h"
> #include "dump.h"
> #include "sysemu.h"
> -#include "bswap.h"
> #include "memory_mapping.h"
> #include "error.h"
> #include "qmp-commands.h"
next prev parent reply other threads:[~2012-06-11 1:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 13:45 [Qemu-devel] [PATCH] w32: Fix broken build (missing include file) Stefan Weil
2012-06-09 11:28 ` Blue Swirl
2012-06-11 1:57 ` Wen Congyang [this message]
2012-06-11 4:58 ` Paolo Bonzini
2012-06-12 7:12 ` Markus Armbruster
2012-06-16 18:07 ` Artyom Tarasenko
2012-06-16 18:31 ` Andreas Färber
2012-06-16 18:48 ` Artyom Tarasenko
2012-07-01 14:26 ` Paolo Bonzini
2012-07-03 18:50 ` Blue Swirl
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=4FD550A4.4030808@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=aliguori@us.ibm.com \
--cc=lcapitulino@redhat.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 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).