From: Paolo Bonzini <pbonzini@redhat.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: amit.shah@redhat.com, peter.crosthwaite@xilinx.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-char: really fix behavior on can_read = 0
Date: Mon, 08 Apr 2013 16:08:58 +0200 [thread overview]
Message-ID: <5162CF7A.5070202@redhat.com> (raw)
In-Reply-To: <5162CF69.2050509@redhat.com>
Il 08/04/2013 16:08, Hans de Goede ha scritto:
>
>> I misread the glib manual, g_source_remove does not let you re-attach
>> the source later. This behavior (called "blocking" the source in glib)
>> is present in glib's source code, but private and not available outside
>> glib;
>
> Hmm, have you filed a bug upstream asking them to make this available
> outside of glib? Would be useful to have...
No, I never had much success asking for new glib APIs.
Paolo
next prev parent reply other threads:[~2013-04-08 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 13:03 [Qemu-devel] [PATCH] qemu-char: really fix behavior on can_read = 0 Paolo Bonzini
2013-04-08 13:56 ` Anthony Liguori
2013-04-08 14:08 ` Hans de Goede
2013-04-08 14:08 ` Paolo Bonzini [this message]
2013-04-08 21:55 ` Anthony Liguori
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=5162CF7A.5070202@redhat.com \
--to=pbonzini@redhat.com \
--cc=amit.shah@redhat.com \
--cc=hdegoede@redhat.com \
--cc=peter.crosthwaite@xilinx.com \
--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 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).