Message ID | 20230304041932.847133-1-wei.w.wang@intel.com |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:5915:0:0:0:0:0 with SMTP id v21csp778296wrd; Fri, 3 Mar 2023 21:12:11 -0800 (PST) X-Google-Smtp-Source: AK7set9ZsCa/zfBmixTZU0Mf5N47avco3X9jQJsyBeiROobB+3kxhfxOSdtUe5cd4miJ/9I5y0ce X-Received: by 2002:a17:906:edd6:b0:906:4739:d73e with SMTP id sb22-20020a170906edd600b009064739d73emr7769469ejb.2.1677906731373; Fri, 03 Mar 2023 21:12:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1677906731; cv=none; d=google.com; s=arc-20160816; b=Hs6kvNRZKMTxmiL0n26YoZwhH/JFPvoeZG1bwUZjTMC5wIsO6p0B9XJ4H8OXW1wKsB S5Yo1qIioRpl85V4LucjZPg/i1TsAPzSAVxo9JAET7VGBP0Da+gUARMZFrMhB/RUEy24 4aHPrctNr8aUQSbvkVpifR1+vICiKmSxv5lTG/dzMSFQfGBKqSoMLqTvQ8Q/NkTGXNsJ YnjgrNSBVT1+zdQ2seiASzRtlJM5QsqgVrTstGz85FiE/w/BxLT818JrJpkVfHaZO/Sx S1seZgF4ES3ys1vILlHCYSwdyV2626Eg6s5NrAuBZuvFby09JPUj9sp2jbSr5T8shsuH uVyw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=7y7FTPii7Y03G8z7Ix346TZYNv0E1NVOEX8sz6ZrDZg=; b=k5sgcZiG0UONO4ZoLn2R7JESYU4PGLpQEV1H9ZKubCJ+HdaJu1ycsML/JLTdTld1va oQHgbI157uU9BoJJ+96JnGIOqgnkwuUvyLXKiJgnGskjdXiJMgh1W5wxi/hkS9h9eYHN 3dU0aZXAX0roJ///KQzqe/OLRzQRbmKLMO/WUjDdzybGsZRb3oye+hX1Q0xYQAnWaXKV J6iWNDgbKSoABiCu8VEguwXqGe106hozwxd6940R//hjiyQtHCxxkrG/kW6QqgDZ0Xgh hyNFtz7Kpl4ln70G818nmyGgvT7aSs7oQO0w0Rhicc1xj5RK/l9VyqPdaIqTzCLdrnOH ZGrg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=BKEMVqwP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d25-20020a056402079900b004ab4c6f9996si869451edy.516.2023.03.03.21.11.47; Fri, 03 Mar 2023 21:12:11 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=BKEMVqwP; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229568AbjCDETl (ORCPT <rfc822;ouuuleilei@gmail.com> + 99 others); Fri, 3 Mar 2023 23:19:41 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52132 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229455AbjCDETj (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Fri, 3 Mar 2023 23:19:39 -0500 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 853611027D for <linux-kernel@vger.kernel.org>; Fri, 3 Mar 2023 20:19:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1677903578; x=1709439578; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=DxbG3dnwzdgNhDUdBwaOLbn/TlHpTsT3olEm03AKNx8=; b=BKEMVqwPGqmSC2P44gsRgghEHsFqQ3qvN0UN6kiUbr6ttG8qthp2o9tm Rsoyo/f6f9kk8W/Scc3HpbBt9M3u8YxUw24iGEwFvyNJE2pVb0MEG51o0 394vUVUZ7dZq8+Nw6Y4C9AJRWFH9Vttn3+fuj6b+2r2oa1vb742I+vQGy H3TXL+3dGynCZo+pHQIP4r9CeVpaSJwNKsuwuNZDqPlF+aBg9E5gfdrFk DZvr0agP9GhwFZKAa9ennSjT1s+hDPEE/XzF9A0YWhYPpgAcv1E+hglHf gaZ8D0GuSAtH+EVKZHT3fW+7eoChp6ppwbb/26lB87QX0R28FG9KpRPO0 A==; X-IronPort-AV: E=McAfee;i="6500,9779,10638"; a="315618074" X-IronPort-AV: E=Sophos;i="5.98,232,1673942400"; d="scan'208";a="315618074" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Mar 2023 20:19:38 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10638"; a="708061997" X-IronPort-AV: E=Sophos;i="5.98,232,1673942400"; d="scan'208";a="708061997" Received: from tdx-lm.sh.intel.com ([10.239.53.27]) by orsmga001.jf.intel.com with ESMTP; 03 Mar 2023 20:19:34 -0800 From: Wei Wang <wei.w.wang@intel.com> To: arnd@arndb.de, akpm@linux-foundation.org, keescook@chromium.org, herbert@gondor.apana.org.au, josh@joshtriplett.org, jani.nikula@intel.com, corbet@lwn.net, jgg@mellanox.com, dmatlack@google.com, mizhang@google.com, pbonzini@redhat.com, seanjc@google.com Cc: linux-kernel@vger.kernel.org, Wei Wang <wei.w.wang@intel.com> Subject: [PATCH v1 0/3] Regarding using 'bool' appropriately Date: Sat, 4 Mar 2023 12:19:29 +0800 Message-Id: <20230304041932.847133-1-wei.w.wang@intel.com> X-Mailer: git-send-email 2.27.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1759412728536898880?= X-GMAIL-MSGID: =?utf-8?q?1759412728536898880?= |
Series | Regarding using 'bool' appropriately | |
Message
Wang, Wei W
March 4, 2023, 4:19 a.m. UTC
When I'm working on patch 3 to change WARN/WARN_ON to use bool for __ret_warn_on according to the documentation in CodingStyle about using 'bool', compiler reports an error from tpm2_key_encode(), and the root cause is that it names a variable 'bool' which conficts with the data type name 'bool'. So fix it and add a rule in CodingStyle to avoid such naming that causes confusion. This is also the reason that the three patches are grouped into one patchset. Wei Wang (3): security: keys: don't use data type as variable name Documentation/CodingStyle: do not use data type names as variable names bug: use bool for __ret_warn_on in WARN/WARN_ON Documentation/process/coding-style.rst | 3 +++ include/asm-generic/bug.h | 12 ++++++------ security/keys/trusted-keys/trusted_tpm2.c | 5 +++-- tools/include/asm/bug.h | 10 +++++----- 4 files changed, 17 insertions(+), 13 deletions(-)