Hi,
> > The two patches conflict with each other, so it's probably easiest if
> > one of Gerd or Markus takes both.
>
> I can squeeze in review and a pull request today. Gerd, if you'd prefer
> to do it yourself, let me know.
Fine with me, go ahead.
Reviewed-by: Gerd Hoffmann
cheers,
Ger
On 08/08/2016 11:45, Markus Armbruster wrote:
> Paolo Bonzini writes:
>
>> On 01/08/2016 13:23, marcandre.lur...@redhat.com wrote:
>>> From: Marc-André Lureau
>>>
>>> Since aa5cb7f5e, the chardevs are being cleaned up when leaving qemu,
>>> before the atexit() handlers. audio_cleanup() may use
Paolo Bonzini writes:
> On 01/08/2016 13:23, marcandre.lur...@redhat.com wrote:
>> From: Marc-André Lureau
>>
>> Since aa5cb7f5e, the chardevs are being cleaned up when leaving qemu,
>> before the atexit() handlers. audio_cleanup() may use the monitor to
>> notify of changes. For compatibility
Hi
- Original Message -
> From: Marc-André Lureau
>
> Since aa5cb7f5e, the chardevs are being cleaned up when leaving qemu,
> before the atexit() handlers. audio_cleanup() may use the monitor to
> notify of changes. For compatibility reasons, let's clean up audio
> before the monitor so
On 01/08/2016 13:23, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Since aa5cb7f5e, the chardevs are being cleaned up when leaving qemu,
> before the atexit() handlers. audio_cleanup() may use the monitor to
> notify of changes. For compatibility reasons, let's clean up audio
From: Marc-André Lureau
Since aa5cb7f5e, the chardevs are being cleaned up when leaving qemu,
before the atexit() handlers. audio_cleanup() may use the monitor to
notify of changes. For compatibility reasons, let's clean up audio
before the monitor so it keeps emitting monitor events.
The audio_
