From: Igor Mitsyanko <i.mitsyanko@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-trivial@nongnu.org, pbonzini@redhat.com,
aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] osdep.h: include sys/types.h for ssize_t definition
Date: Fri, 10 May 2013 19:40:08 +0400 [thread overview]
Message-ID: <518D14D8.9040300@gmail.com> (raw)
In-Reply-To: <CAFEAcA_zpWNN0uPb3pYUxGw4USX8+NFS4_+b4MO8uBdwDEDLwA@mail.gmail.com>
On 05/10/2013 07:24 PM, Peter Maydell wrote:
> On 10 May 2013 16:16, Igor Mitsyanko <i.mitsyanko@gmail.com> wrote:
>> This fixes build for mingw32
>>
>> Signed-off-by: Igor Mitsyanko <i.mitsyanko@gmail.com>
>> ---
>> include/qemu/osdep.h | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/include/qemu/osdep.h b/include/qemu/osdep.h
>> index 42545bc..17946a3 100644
>> --- a/include/qemu/osdep.h
>> +++ b/include/qemu/osdep.h
>> @@ -163,6 +163,8 @@ int qemu_create_pidfile(const char *filename);
>> int qemu_get_thread_id(void);
>>
>> #ifndef CONFIG_IOVEC
>> +#include <sys/types.h>
>> +
> This is quite a long way down to have a system #include.
>
> Can we just take the existing include of sys/types.h at
> the top of the file out of its current #ifdef __OpenBSD__
> guard ?
>
> (http://hacks.owlfolio.org/header-survey/ has a full row
> of greens for sys/types.h so this should be safe.)
>
> thanks
> -- PMM
Nice link.
Long way, yes, but there's "#include <sys/uio.h>" even further down in
this file. But I guess taking existing sys/types.h is still better, I'll
resend it.
prev parent reply other threads:[~2013-05-10 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 15:16 [Qemu-devel] [PATCH] osdep.h: include sys/types.h for ssize_t definition Igor Mitsyanko
2013-05-10 15:24 ` Peter Maydell
2013-05-10 15:40 ` Igor Mitsyanko [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=518D14D8.9040300@gmail.com \
--to=i.mitsyanko@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 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).