qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 2/2] char: report frontend open/closed state in


From: Luiz Capitulino
Subject: Re: [Qemu-devel] [PATCH 2/2] char: report frontend open/closed state in 'query-chardev'
Date: Wed, 25 Jun 2014 09:16:22 -0400

On Wed, 25 Jun 2014 07:14:08 -0600
Eric Blake <address@hidden> wrote:

> On 06/25/2014 07:02 AM, Luiz Capitulino wrote:
> > On Tue, 24 Jun 2014 08:36:36 -0600
> > Eric Blake <address@hidden> wrote:
> > 
> >> [cc'ing Luiz]
> >>
> >> On 06/24/2014 08:21 AM, Laszlo Ersek wrote:
> >>> On 05/29/14 23:05, Eric Blake wrote:
> >>>> On 05/29/2014 02:43 PM, Laszlo Ersek wrote:
> >>
> >>>>> In this series I try to implement the ideas that (I believe) were
> >>>>> suggested by Gerd and Amit in
> >>>>> <https://bugzilla.redhat.com/show_bug.cgi?id=1080376>.
> >>>>>
> 
> >>>
> >>> I'm thinking about resuming work on this. Wenchao's series has been
> >>> applied (ends at commit 75175173). We're between soft and hard freeze
> >>> now. Should I aim at 2.1 or 2.2?
> >>
> >> This series was posted before soft freeze, but adds a new feature.  If
> >> we're going to get it in the 2.1 release, it must be before hard freeze.
> >>  I'll leave it up to Luiz whether a QMP addition this late in the game
> >> is safe to take, although my personal opinion is that since it was
> >> proposed before soft freeze, and DOES make life easier for libvirt, it
> >> is worth a strong consideration.
> > 
> > Has this series being reviewed?
> 
> v1 was reviewed pre-freeze; Laszlo has not yet posted v2 (in part
> because it was waiting on the qapi-as-event series which is now finally
> upstream).

I'm fine with having it for 2.1. It would be great if v2 is posted today or
tomorrow.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]