From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:46581) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QRKE9-0004X9-IK for qemu-devel@nongnu.org; Tue, 31 May 2011 04:23:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QRKE7-0005b3-VY for qemu-devel@nongnu.org; Tue, 31 May 2011 04:23:01 -0400 Received: from mail-yi0-f45.google.com ([209.85.218.45]:44814) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QRKE7-0005am-TC for qemu-devel@nongnu.org; Tue, 31 May 2011 04:22:59 -0400 Received: by yib19 with SMTP id 19so2020149yib.4 for ; Tue, 31 May 2011 01:22:59 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <4DE49DB7.30600@web.de> References: <4DE120BE.1010602@web.de> <4DE37551.6060502@siemens.com> <4DE48689.7070606@web.de> <4DE49DB7.30600@web.de> Date: Tue, 31 May 2011 16:22:59 +0800 Message-ID: From: BrillyWu Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Qemu-devel] [PATCH uq/master V2] kvm: Add CPUID support for VIA CPU List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: kvm@vger.kernel.org, KaryJin@viatech.com.cn, mst@redhat.com, mtosatti@redhat.com, BrillyWu@viatech.com.cn, qemu-devel@nongnu.org, Blue Swirl , avi@redhat.com > >> Blue, this does not trigger the missing braces warning: > > > > Do you mean the bug is that it can not trigger missing > braces warining? > > The script fails to detect missing braces as marked below. > > > It seems that there is no missing braces in my patch, but some > > unnecessary braces. > > There are no unnecessary braces according to QEMU coding style. Oh, I see. Thank you! > >> + index = env->cpuid_xlevel; > >> + } > >> + } else > >> + index = env->cpuid_xlevel; > > This should be: > > } else { > index = ... > } > > >> + } > > Nope, see above. It looks that I should add the missing braces. > > > BTW, I have submited a patch v3 a few minutes before withou > fixing up > > the braces, and I have tested it with my mail client this > time, so it > > could be OK now. > > Yes, your mail client works fine as far as I can see. Yes, you are right. It seems to be the problem of my editor. I'll check whether other places need any brace, and then send it to the patch v3 thread.