qemu-devel
[Top][All Lists]
Advanced

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

Re: [PATCH 00/55] qdev: Rework how we plug into the parent bus


From: Markus Armbruster
Subject: Re: [PATCH 00/55] qdev: Rework how we plug into the parent bus
Date: Mon, 08 Jun 2020 12:56:49 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)

Paolo Bonzini <pbonzini@redhat.com> writes:

> On 19/05/20 16:54, Markus Armbruster wrote:
>> Paolo recently suggested "to move the bus argument (and thus
>> qdev_set_parent_bus) to qdev_init"[1], and that it "would be quite
>> large but hopefully scriptable"[2].  Nerd sniped!
>> 
>> The series is big, but at least the bigger patches are all mechanical.
>> 
>> It is based on my "[PATCH 00/24] Fixes around device realization".
>> 
>> I'm abstaining from cc'ing maintainers on mechanical conversions.  I
>> still cc: for patches I deem interesting, with related patches thrown
>> in for context.  Let me know if you think I should cc: more widely.
>> 
>> PATCH 01-02          Preliminary cleanup
>> PATCH 03             New qdev infrastructure
>>                      Commit message explains why the current state is
>>                      problematic, and how my work improves it.
>> PATCH 04-11          Convert direct users of qdev
>> PATCH 12-16          Convert PCI
>> PATCH 17-20          Convert ISA
>> PATCH 21-24          Convert SSI
>> PATCH 25-28          Convert USB
>> PATCH 29             Garbage collection
>> PATCH 30-32          Convert aux-bus
>> PATCH 33-40          Clean up around child device initialization
>> PATCH 41-49          Convert sysbus
>> PATCH 50             Stop pretending recursive realization is about to become
>>                      real
>> PATCH 51-53          Convert bus-less devices
>> PATCH 54     Garbage collection
>> PATCH 55     Maintain MAINTAINERS
>
> Great stuff, I only had some comments on the commit messages.  I still
> have to review patches 47 and 48 more corefully.

Does this translate into any Reviewed-bys?  On v2, maybe?




reply via email to

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