From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
"Daniel P. Berrange" <berrange@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v2 0/9] Introduce I/O channels framework
Date: Thu, 17 Dec 2015 17:44:43 +0100 [thread overview]
Message-ID: <5672E67B.3010907@redhat.com> (raw)
In-Reply-To: <CAFEAcA9FfVcXtouzuLmdmYqPED8jp1JvH+PC2A9csZdKEaeVvw@mail.gmail.com>
On 17/12/2015 17:40, Peter Maydell wrote:
> Glib's g_source_set_name was only introduced in 2.26,
> and we have to support 2.22.
>
> lseek64 doesn't exist on OSX.
And unnecessary on Linux too, since we compile with
-D_LARGEFILE_SOURCE/-D_FILE_OFFSET_BITS=64.
Paolo
next prev parent reply other threads:[~2015-12-17 16:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 15:40 [Qemu-devel] [PULL v2 0/9] Introduce I/O channels framework Daniel P. Berrange
2015-12-17 15:40 ` [Qemu-devel] [PULL v2 1/9] io: add abstract QIOChannel classes Daniel P. Berrange
2015-12-17 15:40 ` [Qemu-devel] [PULL v2 2/9] io: add helper module for creating watches on FDs Daniel P. Berrange
2015-12-17 15:40 ` [Qemu-devel] [PULL v2 3/9] io: add QIOTask class for async operations Daniel P. Berrange
2015-12-17 15:40 ` [Qemu-devel] [PULL v2 4/9] io: add QIOChannelSocket class Daniel P. Berrange
2015-12-17 15:40 ` [Qemu-devel] [PULL v2 5/9] io: add QIOChannelFile class Daniel P. Berrange
2015-12-17 15:40 ` [Qemu-devel] [PULL v2 6/9] io: add QIOChannelTLS class Daniel P. Berrange
2015-12-17 15:40 ` [Qemu-devel] [PULL v2 7/9] io: add QIOChannelWebsock class Daniel P. Berrange
2015-12-17 15:40 ` [Qemu-devel] [PULL v2 8/9] io: add QIOChannelCommand class Daniel P. Berrange
2015-12-17 15:40 ` [Qemu-devel] [PULL v2 9/9] io: add QIOChannelBuffer class Daniel P. Berrange
2015-12-17 16:40 ` [Qemu-devel] [PULL v2 0/9] Introduce I/O channels framework Peter Maydell
2015-12-17 16:44 ` Paolo Bonzini [this message]
2015-12-17 16:47 ` Daniel P. Berrange
2015-12-17 18:32 ` Paolo Bonzini
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=5672E67B.3010907@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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.