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

Re: [Xen-devel] [Qemu-devel] [PATCH 1/4] Introduce a new hotplug state: Force eject.

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
From: Anthony PERARD <anthony.perard@xxxxxxxxxx>
Date: Tue, 15 May 2012 19:25:34 +0100
Cc: Xen Devel <xen-devel@xxxxxxxxxxxxx>, QEMU-devel <qemu-devel@xxxxxxxxxx>, Anthony Liguori <anthony@xxxxxxxxxxxxx>, "Michael S. Tsirkin" <mst@xxxxxxxxxx>
Delivery-date: Tue, 15 May 2012 18:26:32 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On Tue, May 15, 2012 at 7:19 PM, Stefano Stabellini
<stefano.stabellini@xxxxxxxxxxxxx> wrote:
>
> Given that it is supposed to be a state rather than an action, it should
> be called PCI_FORCE_DISABLED or something like that.

Ok, I will change to that.

Thanks,

-- 
Anthony PERARD

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

References:
- [Xen-devel] [PATCH 1.1 0/4] Xen: Fix PV-on-HVM
  - From: Anthony PERARD
- [Xen-devel] [PATCH 1/4] Introduce a new hotplug state: Force eject.
  - From: Anthony PERARD
- Re: [Xen-devel] [PATCH 1/4] Introduce a new hotplug state: Force eject.
  - From: Stefano Stabellini

Prev by Date: Re: [Xen-devel] [Qemu-devel] [PATCH 2/4] qdev: Introduce qdev_force_unplug.
Next by Date: [Xen-devel] Xen 3.3.x on recent dom0 kernels
Previous by thread: Re: [Xen-devel] [PATCH 1/4] Introduce a new hotplug state: Force eject.
Next by thread: Re: [Xen-devel] [PATCH 1/4] Introduce a new hotplug state: Force eject.
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.