On Sun, Jul 28, 2013 at 04:59:18PM +0200, Andreas Färber wrote:
> Am 28.07.2013 16:08, schrieb Michael S. Tsirkin:
> > On Sun, Jul 28, 2013 at 03:41:07AM +0200, Andreas Färber wrote:
> >> Hello Michael and Gerd,
> >>
> >> As discussed, this series attempts to clean up PCIe devices fiddling with
> >
Am 28.07.2013 16:08, schrieb Michael S. Tsirkin:
> On Sun, Jul 28, 2013 at 03:41:07AM +0200, Andreas Färber wrote:
>> Hello Michael and Gerd,
>>
>> As discussed, this series attempts to clean up PCIe devices fiddling with
>> individual PCIe VMState fields. It is based on my qom-next queue, containi
Am 28.07.2013 15:44, schrieb Andreas Färber:
> Am 28.07.2013 03:41, schrieb Andreas Färber:
>> Patch 1 assumes the following are equivalent:
>> a) - Struct A
>> - Field Aa
>> ...
>>- Field X
>> ...
>> b) - Struct A
>> - Field Aa
>> ...
>> - Field X
>>
>> Patch 2 re
On Sun, Jul 28, 2013 at 03:41:07AM +0200, Andreas Färber wrote:
> Hello Michael and Gerd,
>
> As discussed, this series attempts to clean up PCIe devices fiddling with
> individual PCIe VMState fields. It is based on my qom-next queue, containing
> type and field changes for PCIe devices.
>
> Pat
Am 28.07.2013 03:41, schrieb Andreas Färber:
> Patch 1 assumes the following are equivalent:
> a) - Struct A
> - Field Aa
> ...
>- Field X
> ...
> b) - Struct A
> - Field Aa
> ...
> - Field X
>
> Patch 2 relies on XHCI not being released yet, thus no compatibiliy
Hello Michael and Gerd,
As discussed, this series attempts to clean up PCIe devices fiddling with
individual PCIe VMState fields. It is based on my qom-next queue, containing
type and field changes for PCIe devices.
Patch 1 assumes the following are equivalent:
a) - Struct A
- Field Aa
