Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id CC313C678D4 for ; Thu, 2 Mar 2023 18:46:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229617AbjCBSqu (ORCPT ); Thu, 2 Mar 2023 13:46:50 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41630 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229451AbjCBSqs (ORCPT ); Thu, 2 Mar 2023 13:46:48 -0500 Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2028A515EE for ; Thu, 2 Mar 2023 10:46:47 -0800 (PST) Received: by mail-pl1-x635.google.com with SMTP id z2so209058plf.12 for ; Thu, 02 Mar 2023 10:46:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; t=1677782806; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=ZFVy1NChotHCYXJVQP117OWHfuZeq72Zl4CyzCN0yEs=; b=E/TPH0VOujJi/1gILhW/BBDnZbA8+X5I8p7gzsGHMMaNFhFsUucvL1r0lSqCbUmiGa zjHNnwXCd/KPsZOjA83iEI4BFemkPoza3O0OwSfzN77hlNrfQ/ik2Yza2mdTB7O+5C95 M1jwKWJF/I/PXx/a6C/14/GIGLZyhhiETCd7IuHcEAhZRAVBgVI2vufFwm96qquV5YEN K+iTt53GlsWdyYgykGSrDOun8EK4D9IGKhrbIs3WpRCxA2DmMEy3SRk+DWk3pJ9oEIMC 6XEbw/t0C2xGp6Ww2lHcUuB6DKascpj75g0ojw7qP+OaleSW/yQBLbPpqjfhdC+u3Qi/ KP+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1677782806; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=ZFVy1NChotHCYXJVQP117OWHfuZeq72Zl4CyzCN0yEs=; b=eJQFJViaZ4EYor6E/GVnLyBhaqfb6IWJvfwIiD1/dAR237jqqmSbX3q70IaEDMoBB+ PBr0ZvDzKxJs9zovJmJmdFyCKrAiajUXrfDdPvK28O1pNHleLOO9sxynpCW73xFX3clV 1AE8lM2cQF/5ZrC4T/mzIi0Autc9M5SugpA3SwI+VgQCnqyCNaBWQSLpQMEIF/Ci02is oeCJBf4HcY41hHYFEOYTc4d6QnfLp8tZcH4nCXR08sXyT0Bg+8oba+D8diZldHa4GO4N t9F+ORyq/5QQsDO4ceq2G3aqAHQ+r30hWIsZdyXb2+PKzTA8x46Ig5aagGfrYvavOGPj +zqA== X-Gm-Message-State: AO0yUKXKV71LW1sKfMMro6AI0aaw7jYvDmQS455tCnCC9b3iSFakX/6L WQwf+T3RXAOyjfSrosWGGFK8aQ== X-Google-Smtp-Source: AK7set8944u/7OAA9BNVygtciGCBE+hUBln/eftAicEsEPtx7EZ06zucDbjYpwuXA1F7RaPborv9Ow== X-Received: by 2002:a17:903:248:b0:19e:748c:d419 with SMTP id j8-20020a170903024800b0019e748cd419mr2560811plh.46.1677782806139; Thu, 02 Mar 2023 10:46:46 -0800 (PST) Received: from google.com (77.62.105.34.bc.googleusercontent.com. [34.105.62.77]) by smtp.gmail.com with ESMTPSA id jy8-20020a17090342c800b001990e1aeae4sm49221plb.47.2023.03.02.10.46.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 02 Mar 2023 10:46:45 -0800 (PST) Date: Thu, 2 Mar 2023 18:46:42 +0000 From: Mingwei Zhang To: Sean Christopherson Cc: Paolo Bonzini , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , Sagi Shahar , Erdem Aktas , Peter Shier , Anish Ghulati , Oliver Upton , James Houghton , Anish Moorthy , Ben Gardon , David Matlack , Ricardo Koller , Axel Rasmussen , Aaron Lewis , Ashish Kalra , Babu Moger , Chao Gao , Chao Peng , Chenyi Qiang , David Woodhouse , Emanuele Giuseppe Esposito , Gavin Shan , Guang Zeng , Hou Wenlong , Jiaxi Chen , Jim Mattson , Jing Liu , Junaid Shahid , Kai Huang , Leonardo Bras , Like Xu , Li RongQing , "Maciej S . Szmigiero" , Maxim Levitsky , Michael Roth , Michal Luczaj , Nikunj A Dadhania , Paul Durrant , Peng Hao , Peter Gonda , Peter Xu , Robert Hoo , Suravee Suthikulpanit , Tom Lendacky , Vipin Sharma , Vitaly Kuznetsov , Wanpeng Li , Wei Wang , Xiaoyao Li , Yu Zhang , Zhenzhong Duan , kvm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/2] Documentation/process: Add a maintainer handbook for KVM x86 Message-ID: References: <20230217225449.811957-1-seanjc@google.com> <20230217225449.811957-3-seanjc@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 21, 2023, Sean Christopherson wrote: > On Sat, Feb 18, 2023, Mingwei Zhang wrote: > > On Fri, Feb 17, 2023, Sean Christopherson wrote: > > > +Coding Style > > > +~~~~~~~~~~~~ > > > +When it comes to style, naming, patterns, etc., consistency is the number one > > > +priority in KVM x86. If all else fails, match what already exists. > > > + > > > +With a few caveats listed below, follow the tip tree maintainers' preferred > > > +:ref:`maintainer-tip-coding-style`, as patches/series often touch both KVM and > > > +non-KVM x86 files, i.e. draw the attention of KVM *and* tip tree maintainers. > > > + > > > +Using reverse fir tree for variable declarations isn't strictly required, > > > +though it is still preferred. > > > > What is the 'reverse fir tree'? Maybe, "Reverse Christmas Tree" is > > better to understand. > > For some parts of the world, but not all. For this, I want to follow whatever > description the tip tree uses, which as of today is "reverse fir tree", as this > is really a qualifier on the tip tree rules. Some parts of the world is correct. In fact, in our world, we use 'reverse Christmas Tree' more than the other. Check lore.kernel.org: https://lore.kernel.org/all/?q=reverse+christmas+tree https://lore.kernel.org/all/?q=reverse+fir+tree You will find the former is used 10x more frequent than the latter. Overall, I don't hold a strong opinion immediately after I understand the meaning of 'reverse fir tree' and I do agree that it is safer to follow the Linux Tip Tree Handbook. Also, thanks for the whole guideline. -Mingwei