Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp2191843ybe; Tue, 3 Sep 2019 09:12:34 -0700 (PDT) X-Google-Smtp-Source: APXvYqzqEi9VXurVO1BOJowRx55hxMgn2/Kf4VnFkIQIpQ5E08zrR8Z2FTE50R/0xFuXdHnbvGmq X-Received: by 2002:a17:90a:b292:: with SMTP id c18mr58001pjr.1.1567527154059; Tue, 03 Sep 2019 09:12:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567527154; cv=none; d=google.com; s=arc-20160816; b=WH2Oieczsj3SL42WntZg9mWB7WTxNy9eIjKBhexWHAAAFby1FgWVnYr24lqw6KT4jC 5IwhM4b9qcbFZZLMyIjLfIHEFoMZAs6w7qX7BnUCWgUR35ievfBkIE66SGJj9GO16ou2 kVEVB4jUBErInR5I1sAsNu2dQpno75xXBqEcJIbwlQQrB2aqaS0NLe0VeCbfuzCrftgY 0IpQpDqgybxEvQtsgGnm7+kcFpR7USPGkycpFDZvVMQLzUOifgQog9tM1CGWJiTRnzTV WdWUzS63fTGXejkhJU4PUL48iKP/UtVuBYEAZ0kVp2z1/vvSv+7wfEcZBpX29iK0/kwi 1/sQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:organization:references:in-reply-to:date:cc:to:from :subject:message-id; bh=bg55QW5QAbb4JouraEOgoXyxVtNCETvcU+Ey5Emkk4c=; b=cQfmhHf6iYnoqdYwGDVlJXjhJDC5k2m+Iiqp1mDKwLGZWn1kizkWofKcMEB7yHotEM sfXra2Jsua+cI3drd1eBv5FbRAaHypgN/qT56PqRWZ9qjxETqGyCF28NSV8d+Uruw/NN DmJZsK+aiAg9TPCFFHoCn81lslgHitvD7xfr0vBSq7z5ZcRghjrwjpn6f8mCTuXblD5D AQ9EfV0IMamzzNT66Agw8PIem+IUfpQgEa78ZCKB/dzZLRHPxM5zOIeJa1m380mhIMHZ CRDB8hQoiPmxXQmFVc+lfbDygm6DH6XLNIumKSUZgCqoiFZqaM/npUb4w8KoGPyeUZiA 5IXA== 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 f37si12640875pgb.262.2019.09.03.09.12.16; Tue, 03 Sep 2019 09:12:34 -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 S1729972AbfICQK4 (ORCPT + 99 others); Tue, 3 Sep 2019 12:10:56 -0400 Received: from mga11.intel.com ([192.55.52.93]:60358 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728679AbfICQK4 (ORCPT ); Tue, 3 Sep 2019 12:10:56 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Sep 2019 09:10:55 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,463,1559545200"; d="scan'208";a="184803149" Received: from vkuppusa-mobl2.ger.corp.intel.com ([10.252.39.67]) by orsmga003.jf.intel.com with ESMTP; 03 Sep 2019 09:10:51 -0700 Message-ID: Subject: Re: [PATCH 2/2] tpm: tpm_crb: enhance resource mapping mechanism for supporting AMD's fTPM From: Jarkko Sakkinen To: Seunghun Han Cc: "Safford, David (GE Global Research, US)" , Jason Gunthorpe , Peter Huewe , "open list:TPM DEVICE DRIVER" , Linux Kernel Mailing List Date: Tue, 03 Sep 2019 19:10:50 +0300 In-Reply-To: References: <20190830095639.4562-1-kkamagui@gmail.com> <20190830095639.4562-3-kkamagui@gmail.com> <20190830124334.GA10004@ziepe.ca> <20190902135348.3pndbtbi6hpgjpjn@linux.intel.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.32.2-1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2019-09-03 at 07:42 +0900, Seunghun Han wrote: > I have a question. Do you think this patch is not enough to handle > AMD's fTPM problem? If so, would you tell me about it? I will change > my patch. I have no new feedback to give at this point and no absolutely time to brainstorm new ideas. You've now sent the same patch set version twice. The one that was sent 8-30 has the same patch version and no change log so no action taken from my part. Please version your patch sets and keep the change log in the cover letter. /Jarkko