linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Pavel Tatashin <pasha.tatashin@soleen.com>,
	jmorris@namei.org, peterhuewe@gmx.de, jgg@ziepe.ca,
	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,
	tee-dev@lists.linaro.org, ilias.apalodimas@linaro.org,
	sumit.garg@linaro.org, rdunlap@infradead.org
Subject: Re: [PATCH v3] tpm/tpm_ftpm_tee: add shutdown call back
Date: Thu, 17 Oct 2019 14:06:44 -0400	[thread overview]
Message-ID: <20191017180644.GW31224@sasha-vm> (raw)
In-Reply-To: <20191017162251.GB6667@linux.intel.com>

On Thu, Oct 17, 2019 at 07:22:51PM +0300, Jarkko Sakkinen wrote:
>On Wed, Oct 16, 2019 at 12:31:14PM -0400, Pavel Tatashin wrote:
>> Add shutdown call back to close existing session with fTPM TA
>> to support kexec scenario.
>>
>> Add parentheses to function names in comments as specified in kdoc.
>>
>> Signed-off-by: Thirupathaiah Annapureddy <thiruan@microsoft.com>
>> Signed-off-by: Pavel Tatashin <pasha.tatashin@soleen.com>
>
>LGTM
>
>Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
>
>I have no means to test this though. It still needs a tested-by.

We've been running this patch internally for the past few months,
testing kexec scenarios, so I guess it could have mine :)

Tested-by: Sasha Levin <sashal@kernel.org>

-- 
Thanks,
Sasha

      reply	other threads:[~2019-10-17 18:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16 16:31 [PATCH v3] tpm/tpm_ftpm_tee: add shutdown call back Pavel Tatashin
2019-10-17 16:22 ` Jarkko Sakkinen
2019-10-17 18:06   ` Sasha Levin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191017180644.GW31224@sasha-vm \
    --to=sashal@kernel.org \
    --cc=bryankel@microsoft.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=jgg@ziepe.ca \
    --cc=jmorris@namei.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=peterhuewe@gmx.de \
    --cc=rdunlap@infradead.org \
    --cc=sumit.garg@linaro.org \
    --cc=tee-dev@lists.linaro.org \
    --cc=thiruan@microsoft.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).