Received: by 2002:a05:6358:489b:b0:bb:da1:e618 with SMTP id x27csp6836686rwn; Tue, 13 Sep 2022 09:37:22 -0700 (PDT) X-Google-Smtp-Source: AA6agR52VAP+A5tguScV1+YRx14AiM1iPW9b4PHJ+pkd+vaJXbbdpPwrAWz8z7bU7JCZWGsyuQhK X-Received: by 2002:a17:907:968c:b0:77c:c5c7:26b7 with SMTP id hd12-20020a170907968c00b0077cc5c726b7mr8511631ejc.171.1663087042245; Tue, 13 Sep 2022 09:37:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1663087042; cv=none; d=google.com; s=arc-20160816; b=rWb0bjJuxAvsiHnwITZTe2qKijMh/RKmJa9qo9Px/Y5I8RGo1WjL/wFba5yE1cIDGw 2HokgAN+c7ztjWQa425xd7/g1EgfqtBOX205dNODg/+VZP0HkuafScMb4FvbLrZkFleB ORNqRio2b8XjNjRZJ92rPDcmls1b2uFxwWyx7T8U9/ZuciRagGOtumsM9ecs9muq2Lzo K5ccywpZlaO5h/0AZKefwKXSQX+jLhWqEcUWQwvXsYZdSoE3F45gCtK8hjFNCiVgNh1F gA3KeQaovawhT9S61JaEgMQ3DeqqzFYj+9N1AatiMS28fJbElbgyX7Fl0CMd7i7D6xvg dCGA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=653QMBYd1FJQcAfErP+Knm09bUzwmFuXixLeJJ50f94=; b=vF8EHC35JxJZOdO786Ro4azp2N2p/tfB4qDGPSjwiZyK5AFJ73GFkK6E7/6stWaTyK s7RwXOrsZYu1Ap3+MrTg3FjRJyEyCoaZaeOL6lfTaYXpwdaPiu9qNd7DCWyYcIjsEYlZ xyzdcfz4S+ctKBlXUW5ZlrWcZSpyMo76JGHy9KnEMuUqe/cre8l/4GZ4d6nNyXkm8u8Q Qd/IPow2jy9YSaQEnk/ceWo3CKZ1AFkmYv+aSqsoN0WNhTJ7Gjax2PGsApmFcTFzjPW8 GOMh+3evx1ukEWDrZc6/9iyUQiSHLnkvEa5NKoHOUMz6ShlEzSUNj2kqiIjJkXXb0dDe iMIg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=J7nmIPvc; 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id l11-20020a056402254b00b00447f0236543si10675333edb.514.2022.09.13.09.36.55; Tue, 13 Sep 2022 09:37:22 -0700 (PDT) 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=J7nmIPvc; 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 S231376AbiIMQ20 (ORCPT + 99 others); Tue, 13 Sep 2022 12:28:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54998 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232009AbiIMQ15 (ORCPT ); Tue, 13 Sep 2022 12:27:57 -0400 Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7AC80AE208; Tue, 13 Sep 2022 08:23:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1663082615; x=1694618615; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=Xv3LSLJmI60OwaQZNgO6wmG3l4up4OQb63JFCEM8X4Q=; b=J7nmIPvcJmoGibWc1aqkwUtC6QNghmadigMSA6jhq/wl8GHQzgcPjVAV QZSGS3NMJtxkts268Y3y7L9bs0UkSyKesx/aBX0qIiWugVhM93J4Tr0wN SOO22aUGtfH2m6SfM4ese9D3llYXqNK+ecsZyUuIb6v3E2yQiu+uR4QIf AehfrUA6iFjiQn8ivPxLPYYSUPcsPoKYGQpwBCIuc4NAJX4bM4//3kqvd RerbOZQgfbDkB8NWU0pofa+XxhFd0sCYd32LPGi1jlwewvEQ8GdgXoUUO vQC6DANfR64EQvVtkKGPSfsoytbS6smHF9GH4blh8xp0/ATLasyjognjt A==; X-IronPort-AV: E=McAfee;i="6500,9779,10469"; a="277897879" X-IronPort-AV: E=Sophos;i="5.93,313,1654585200"; d="scan'208";a="277897879" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Sep 2022 08:21:23 -0700 X-IronPort-AV: E=Sophos;i="5.93,313,1654585200"; d="scan'208";a="646969211" Received: from liweian-mobl.amr.corp.intel.com (HELO [10.209.26.112]) ([10.209.26.112]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Sep 2022 08:21:22 -0700 Message-ID: <11c9a594-4012-c648-829b-6bd410d2415d@linux.intel.com> Date: Tue, 13 Sep 2022 08:21:22 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Thunderbird/91.11.0 Subject: Re: [PATCH v13 1/3] x86/tdx: Add TDX Guest attestation interface driver Content-Language: en-US To: Dave Hansen , "Huang, Kai" , "tglx@linutronix.de" , "mingo@redhat.com" , "shuah@kernel.org" , "x86@kernel.org" , "bp@alien8.de" , "dave.hansen@linux.intel.com" Cc: "linux-kernel@vger.kernel.org" , "ak@linux.intel.com" , "gregkh@linuxfoundation.org" , "wander@redhat.com" , "tim.gardner@canonical.com" , "hpa@zytor.com" , "isaku.yamahata@gmail.com" , "kirill.shutemov@linux.intel.com" , "Luck, Tony" , "khalid.elmously@canonical.com" , "marcelo.cerri@canonical.com" , "Cox, Philip" , "linux-doc@vger.kernel.org" , "linux-kselftest@vger.kernel.org" References: <20220909192708.1113126-1-sathyanarayanan.kuppuswamy@linux.intel.com> <20220909192708.1113126-2-sathyanarayanan.kuppuswamy@linux.intel.com> <4a4ed638-d505-6f30-bf0f-a16a32d494a4@intel.com> From: Sathyanarayanan Kuppuswamy In-Reply-To: <4a4ed638-d505-6f30-bf0f-a16a32d494a4@intel.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.9 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_MED, SPF_HELO_PASS,SPF_NONE,T_SCC_BODY_TEXT_LINE 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: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 9/13/22 2:01 AM, Dave Hansen wrote: > On 9/12/22 19:44, Sathyanarayanan Kuppuswamy wrote: >>> and include the header ( ?) for memchr_inv()? >> One of the previous headers includes linux/string.h (I am not sure which one). >> So why include it explicitly? > Because it's a best practice. What happens is that you ride along on > the coat tails of another #include, someone sees that include is no > longer used and removes it. Then, your code is busted on some weird > .config. > > *OR*, the header itself changes and doesn't #include the dependency you > need. > > I guess you can go add this advice to Documentation/ if it's not there > already somewhere. Ok. I will include it explicitly. -- Sathyanarayanan Kuppuswamy Linux Kernel Developer