qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH v11 00/34] modify boot order of guest, and take


From: Michael Mueller
Subject: Re: [Qemu-devel] [PATCH v11 00/34] modify boot order of guest, and take effect after rebooting
Date: Thu, 9 Oct 2014 13:07:36 +0200

On Thu, 09 Oct 2014 11:47:12 +0200
Gerd Hoffmann <address@hidden> wrote:

> On Mi, 2014-10-08 at 19:00 +0800, Gonglei wrote:
> > On 2014/10/7 16:00, Gonglei (Arei) wrote:
> > 
> > > From: Gonglei <address@hidden>
> > > 
> > > Changes since v10:
> > >  1. add handler for virtio-blk-pci/s390/ccw in PATCH 28.
> > >  2. add especial bootidnex setter/getter functions for usb-storage
> > >     device in PATCH 29.
> > >  3. add bootindex qom property for nvma and ne2k_isa devices,
> > >     avoid regrassion in PATCH 30.
> > >  4. change fprintf to error_report in bootdevice.c in PATCH 34.
> > >  5. rebase on the latest qemu master tree.
> > >  6. add 'Reviewed-by' in other patches. (Thanks, Gerd)
> > > 
> > 
> > 
> > Hi, Gerd
> > 
> > Could you please review the v11 and consider to merge this series in your 
> > tree?
> > I have no idea which maintainer can apply this series. It seems that only 
> > you
> > and Eduardo  interested in and reviewed this patch series at present. :(
> 
> Yea, for these cross-tree changes it isn't always clear which way they
> should be merged.  qom or pc would make sense I think.
> 
> I can prepare a pull request too, but I'd like to have a second opinion
> on the stuff which is outside of my primary focus:
> 
>   * fw_cfg changes (mst?  paolo?)
>   * qom bits (andreas?  paolo?, eduardo?)
> 
> I'll go take "no answer" as "no objections", but I'd prefer to apply one
> or another "reviewed-by" to the series.
> 
> thanks,
>   Gerd
> 

The s390x team is planning to use some functionality of this patch set as base 
for diag308
implementation. I'll give v11 a try on our platform.

Michael

> 
> 




reply via email to

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