Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp78576yba; Mon, 20 May 2019 05:19:52 -0700 (PDT) X-Google-Smtp-Source: APXvYqwBmkuIcsV0WNyk5K7nB4C0UOs5TRIeZQnFykTYnepv95yub/xkMyeUi1Fjoqr8C9+pymVW X-Received: by 2002:a62:1692:: with SMTP id 140mr57805143pfw.166.1558354792522; Mon, 20 May 2019 05:19:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558354792; cv=none; d=google.com; s=arc-20160816; b=oLyL+MhWwhhTdzwyvXFuzajQ9SJu+3d2ejSLtmvVoMQEOMMyVzME2gBXdmlxtpYVuH i9fRfWCV+oP7WcB8kxU05ZImJ8iFdfvUfoAGCXgSYdyipTUTrVDnbargnRIcOLSoavYD GTcQGqvKPdMrYWziOkzw8vCdqGcetCnngEa+02L+qf7iEMTh9Us0TKSKsygy+v3Wasro t2Oay+St5sj9scTRyNU+e0EmGXV3b+a79zY6IgoT4MJTaAhuwNIBiKZbLrtdrJ1msSiH x9ugMGSaBYI9QWWbgtB0fELkhV+H8apx2fz192ThCKZxWMkzdCqt5Gjudv+HJ9nwQPf2 mHQw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:organization:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=TKRnnzmM5114uJwf8NsLq8HDkTIoj0a7W7KTAMU1Xsw=; b=Aapic91GYcH47cp2gsetL0yHg6SzNi+2Vz1R7Yxime92TiD3/7QNwosFhgq0bvu6F3 yaUW2iP1hrQvz7jnj5P3wtAoKGgdUX9Jy3YP+YW5BYsRhX23NbFWBGNg0nEQyCXbD7O9 l9xMIm6QokripxtxAvkpB1o9X/hmON8KjcFT526I/NO9jh4v8nRGC3IiuXhco47DmErV 9QLnLwSuQ+pOOKUSoZu3tbQJ6dDqA3ez/CY9xeWY/ne4mGs0KIo9kwHTH2IzFoUU3u92 dYGKf1xGmpEoLnvjxn9JjCf1xO7T7dOG2PrFTSGEGtNzk5LFe2YuR6siX1hQSdc3Rga4 AN4Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s61si15302865plb.259.2019.05.20.05.19.38; Mon, 20 May 2019 05:19:52 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732272AbfETL6e (ORCPT + 99 others); Mon, 20 May 2019 07:58:34 -0400 Received: from mga06.intel.com ([134.134.136.31]:28368 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730727AbfETL6d (ORCPT ); Mon, 20 May 2019 07:58:33 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 May 2019 04:58:33 -0700 X-ExtLoop1: 1 Received: from mhauser-mobl.ger.corp.intel.com (HELO localhost) ([10.252.47.244]) by fmsmga001.fm.intel.com with ESMTP; 20 May 2019 04:58:29 -0700 Date: Mon, 20 May 2019 14:58:27 +0300 From: Jarkko Sakkinen To: Sasha Levin Cc: peterhuewe@gmx.de, jgg@ziepe.ca, corbet@lwn.net, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-integrity@vger.kernel.org, linux-kernel@microsoft.com, thiruan@microsoft.com, bryankel@microsoft.com Subject: Re: [PATCH v3 1/2] ftpm: firmware TPM running in TEE Message-ID: <20190520115827.GG27805@linux.intel.com> References: <20190415155636.32748-1-sashal@kernel.org> <20190415155636.32748-2-sashal@kernel.org> <20190515081250.GA7708@linux.intel.com> <20190517132226.GB11972@sasha-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190517132226.GB11972@sasha-vm> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 17, 2019 at 09:22:26AM -0400, Sasha Levin wrote: > The whole TEE subsystem is already well documented in our kernel tree > (https://www.kernel.org/doc/Documentation/tee.txt) and beyond. I can add > a reference to the doc here, but I'd rather not add a bunch of TEE > related comments as you suggest later in your review. > > The same way a PCI device driver doesn't describe what PCI is in it's > code, we shouldn't be doing the same for TEE here. Thanks for pointing out the documentation! That is sufficient. /Jarkko