Il 07/06/2014 01:50, Peter Crosthwaite ha scritto:
On Sat, Jun 7, 2014 at 12:52 AM, Paolo Bonzini wrote:
Il 06/06/2014 15:36, Peter Crosthwaite ha scritto:
However, I'd rather have the concept bake for a bit by starting with
read-only properties.
The just a matter of pulling our the setter
On Sat, Jun 7, 2014 at 12:52 AM, Paolo Bonzini wrote:
> Il 06/06/2014 15:36, Peter Crosthwaite ha scritto:
>
>>> However, I'd rather have the concept bake for a bit by starting with
>>> read-only properties.
>>
>>
>> The just a matter of pulling our the setters?
>
>
> Yes. You can leave in all th
Il 06/06/2014 15:36, Peter Crosthwaite ha scritto:
However, I'd rather have the concept bake for a bit by starting with
read-only properties.
The just a matter of pulling our the setters?
Yes. You can leave in all the preparatory refactoring.
I guess it can be done
but I don't fully unders
On Fri, Jun 6, 2014 at 7:36 PM, Paolo Bonzini wrote:
> Il 06/06/2014 08:11, Peter Crosthwaite ha scritto:
>
>> Hi Paolo, Andreas,
>>
>> This patch series QOMifies Memory regions. This is the Memory API
>> specific subset of patches forming part of the Memory/GPIO/Sysbus
>> QOMification.
>>
>> I th
Il 06/06/2014 08:11, Peter Crosthwaite ha scritto:
Hi Paolo, Andreas,
This patch series QOMifies Memory regions. This is the Memory API
specific subset of patches forming part of the Memory/GPIO/Sysbus
QOMification.
I think Paolo already has P1 enqeued. Including for ease of review.
some QOM pa
Hi Paolo, Andreas,
This patch series QOMifies Memory regions. This is the Memory API
specific subset of patches forming part of the Memory/GPIO/Sysbus
QOMification.
I think Paolo already has P1 enqeued. Including for ease of review.
some QOM patches in P2-4 that cut down on later boilerplate. TBH
