From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:58442) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RsgYj-00068M-Hj for qemu-devel@nongnu.org; Wed, 01 Feb 2012 15:13:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RsgYf-0002Kr-58 for qemu-devel@nongnu.org; Wed, 01 Feb 2012 15:13:37 -0500 Received: from e7.ny.us.ibm.com ([32.97.182.137]:57700) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RsgYf-0002Km-0v for qemu-devel@nongnu.org; Wed, 01 Feb 2012 15:13:33 -0500 Received: from /spool/local by e7.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 1 Feb 2012 15:13:31 -0500 Received: from d01relay05.pok.ibm.com (d01relay05.pok.ibm.com [9.56.227.237]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 60D5F6E8217 for ; Wed, 1 Feb 2012 15:11:00 -0500 (EST) Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay05.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q11KB0i6253792 for ; Wed, 1 Feb 2012 15:11:00 -0500 Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q11KAxC9006727 for ; Wed, 1 Feb 2012 15:11:00 -0500 Message-ID: <4F299C52.1030809@us.ibm.com> Date: Wed, 01 Feb 2012 14:10:58 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <1327957741-5842-1-git-send-email-aliguori@us.ibm.com> <4F270897.70905@us.ibm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 00/23] qom: use Type system to register all devices List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Paolo Bonzini , Andreas Faerber , qemu-devel@nongnu.org On 02/01/2012 01:55 PM, Peter Maydell wrote: > On 30 January 2012 21:16, Anthony Liguori wrote: >> Patch 8/23 is an automated touch everything patch. > > It's kind of awkward having a patch series that is both long (number > of patches) and wide (patches that require touching/conversion of > every device in the tree), because the length means it needs a long > review time on the list, and the width means it's going to conflict > with lots of other changes (and especially newly arriving device > models). I could certainly split this into three parts. But patches 0-8 aren't terribly meaningful outside of the context of patch 9. And patch 9 by itself leaves the old infrastructure around which means that you would potentially need more patches like patch 9 in a future series. So I don't think this series could really be trimmed by anything more than a couple patches and I don't see a huge advantage in doing that. This sort of changes are the exception, not the common thing. Once this series is merged, things will go back to normal patch series wise. Regards, Anthony Liguori > > -- PMM >