From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:46217) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SCDzM-0006QM-9d for qemu-devel@nongnu.org; Mon, 26 Mar 2012 13:45:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SCDzK-0007PP-C6 for qemu-devel@nongnu.org; Mon, 26 Mar 2012 13:45:51 -0400 Received: from mail-ob0-f173.google.com ([209.85.214.173]:64534) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SCDzK-0007PF-5F for qemu-devel@nongnu.org; Mon, 26 Mar 2012 13:45:50 -0400 Received: by obbwd20 with SMTP id wd20so6275487obb.4 for ; Mon, 26 Mar 2012 10:45:48 -0700 (PDT) Message-ID: <4F70AB4A.8050000@codemonkey.ws> Date: Mon, 26 Mar 2012 12:45:46 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <1332727608-26523-1-git-send-email-liwp@linux.vnet.ibm.com> <4F70A8E2.10508@codemonkey.ws> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 0/6] refactor PC machine, i440fx and piix3 to take advantage of QOM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: qemu-devel@nongnu.org, Anthony Liguori , Wanpeng Li , Avi Kivity , Gavin Shan On 03/26/2012 12:43 PM, Blue Swirl wrote: > On Mon, Mar 26, 2012 at 17:35, Anthony Liguori wrote: >> On 03/26/2012 12:09 PM, Blue Swirl wrote: >>> >>> On Mon, Mar 26, 2012 at 02:06, Wanpeng Li wrote: >>>> >>>> >>>> From: Anthony Liguori >>>> >>>> >>>> This series aggressively refactors the PC machine initialization to be >>>> more >>>> modelled and less ad-hoc. The highlights of this series are: >>> >>> >>> Please fix coding style while moving. >> >> >> I disagree. That makes reviewing the movement and rebasing the movement >> pretty difficult. > > Yes, a separate step would be nice. > >> If we were to fix the issues, it should before or after. But in that >> context, I think it makes it orthogonal to moving the code and should be >> treated independently. > > I'd fix the style in the first patch, then perform moves etc. That way > no patch would add noncompliant code, only remove. Is this something we universally want to do? What would we do about patches to audio? I'd prefer not to go down this road. Let's keep discussion of fixing CODING_STYLE of existing code separate from rearchitecting/enhancing code. Regards, Anthony Liguori > >> Regards, >> >> Anthony Liguori