qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH 1/7] tests: qgraph API for the qtest driver fram


From: Stefan Hajnoczi
Subject: Re: [Qemu-devel] [PATCH 1/7] tests: qgraph API for the qtest driver framework
Date: Fri, 27 Jul 2018 13:54:32 +0100
User-agent: Mutt/1.10.0 (2018-05-17)

On Wed, Jul 18, 2018 at 11:13:18PM +0200, Emanuele wrote:
> 
> 
> On 07/18/2018 09:28 PM, Paolo Bonzini wrote:
> > On 18/07/2018 16:23, Stefan Hajnoczi wrote:
> > > > > > +struct QOSGraphObject {
> > > > > > +    /* for produces, returns void * */
> > > > > > +    QOSGetDriver get_driver;
> > > > > Unused?
> > > > > 
> > > > > > +    /* for contains, returns a QOSGraphObject * */
> > > > > > +    QOSGetDevice get_device;
> > > > > Unused?
> > > > What is unused?
> > > Neither of these fields are used in this patch.  Please introduce them
> > > in the first patch that actually uses them.  This way code review can
> > > proceed linearly and it also prevents deadcode when just part of a patch
> > > series is merged or backported.
> > So do you suggest to squash patch 6 into this one, so that a user of
> > QOSGraphObject exists already here?
> I think he's right, it makes no sense to have qos-graph as patch 6, it could
> go as patch 2, even though by that time no object/node exist yet.
> 
> Moreover, right now no file in patch 3-4-5 is actually compiled until patch
> 6, which is easily prone to errors in case of future edits (I too have this
> problem right now, when I need to modify sdhci.c and I'm forced to return to
> the branch head to compile), so adding it before would make things more
> clear.

Sounds good.

Stefan

Attachment: signature.asc
Description: PGP signature


reply via email to

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