On 2/6/19 12:26 PM, Vladimir Sementsov-Ogievskiy wrote: >>> shows a lot of, exactly 34 after io.c already updated. >>> They are in different subsystems, so I think it should be simpler to push >>> this >>> one as a precedent and example, and then send separate patches (or series) >>> per-maintainer. >> >> Most are block related, so getting it in through the block maintainers >> is probably the easiest - but you ARE right that one patch per one or >> two files or two is going to be smartest (otherwise, it gets too big). >>
>> I'd group qed-table.c and qed.c; and the two hw/ide/ files; resulting in >> 14 more patches to go. >> > > So, you, think better is to make one common patch set? Ok, I'll do (hmm or > start doing) > it tomorrow as v3 if no other opinions. Yes, a v3 series of 16 patches for the entire conversion, and cc: qemu-block, should be sufficient. Looking forward to seeing v3. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
