Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933707AbbKSCxW (ORCPT ); Wed, 18 Nov 2015 21:53:22 -0500 Received: from mga03.intel.com ([134.134.136.65]:27860 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933680AbbKSCxU (ORCPT ); Wed, 18 Nov 2015 21:53:20 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,316,1444719600"; d="scan'208";a="602948442" Subject: Re: [PATCH 02/10] KVM: x86: MMU: Add helper function to clear a bit in unsync child bitmap To: Takuya Yoshikawa , pbonzini@redhat.com References: <20151112204849.ba920599a8426d7196a0df73@lab.ntt.co.jp> <20151112205019.611e8216adebb465b689876e@lab.ntt.co.jp> <564BE628.1050705@linux.intel.com> <564D1EF7.4000707@lab.ntt.co.jp> Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org From: Xiao Guangrong Message-ID: <564D3816.8080609@linux.intel.com> Date: Thu, 19 Nov 2015 10:46:46 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <564D1EF7.4000707@lab.ntt.co.jp> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1889 Lines: 54 On 11/19/2015 08:59 AM, Takuya Yoshikawa wrote: > On 2015/11/18 11:44, Xiao Guangrong wrote: > >> On 11/12/2015 07:50 PM, Takuya Yoshikawa wrote: >>> + if (!ret) { >>> + clear_unsync_child_bit(sp, i); >>> + continue; >>> + } else if (ret > 0) { >>> nr_unsync_leaf += ret; >> >> Just a single line here, braces are unnecessary. >> >>> - else >>> + } else >>> return ret; > > I know we can eliminate the braces, but that does not mean > we should do so: there seems to be no consensus about this > style issue and checkpatch accepts both ways. > > Actually, some people prefer to put braces when one of the > if/else-if/else cases has multiple lines. You can see > some examples in kernel/sched/core.c: see hrtick_start(), > sched_fork(), free_sched_domain(). > > In our case, I thought putting braces would align the else-if > and else and make the code look a bit nicer, but I know this > may be just a matter of personal feeling. > > In short, unless the maintainer, Paolo for this file, has any > preference, both ways will be accepted. The reason why i pointed this out is that it is the style documented in Documentation/CodingStyle: | Do not unnecessarily use braces where a single statement will do. | | if (condition) | action(); | Actually, Ingo Molnar hated this braces-style too much and blamed many developers who used this style (include me, that why i was nervous to see this style :( ). If this style is commonly accepted now, it is worth making a patch to update Documentation/CodingStyle. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/