From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: J Freyensee <why2jjj.linux@gmail.com>, linux-integrity@vger.kernel.org
Cc: linux-security-module@vger.kernel.org, keyrings@vger.kernel.org,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 3/5] tpm: migrate tpm2_probe() to use struct tpm_buf
Date: Sat, 10 Mar 2018 15:11:35 +0200 [thread overview]
Message-ID: <1afb789425c50f06efbd80bc7377731fd1269d42.camel@linux.intel.com> (raw)
In-Reply-To: <3f3f9059-06ae-cb78-0d02-2658b2edc234@gmail.com>
On Thu, 2018-03-08 at 13:47 -0800, J Freyensee wrote:
> Looks better :-).
>
>
> Acked-by: Jay Freyensee <why2jjj.linux@gmail.com>
Thank you.
/Jarkko
next prev parent reply other threads:[~2018-03-10 13:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 16:56 [PATCH v3 0/5] Migrate all TPM 2.0 commands to use struct tpm_buf Jarkko Sakkinen
2018-03-05 16:56 ` [PATCH v3 1/5] tpm: fix intermittent failure with self tests Jarkko Sakkinen
2018-03-12 11:13 ` Jarkko Sakkinen
2018-03-17 1:20 ` James Bottomley
2018-03-19 21:06 ` Jarkko Sakkinen
2018-03-05 16:56 ` [PATCH v3 2/5] tpm: migrate tpm2_shutdown() to use struct tpm_buf Jarkko Sakkinen
2018-03-05 16:56 ` [PATCH v3 3/5] tpm: migrate tpm2_probe() " Jarkko Sakkinen
2018-03-05 22:52 ` Mimi Zohar
2018-03-16 12:21 ` Jarkko Sakkinen
2018-03-16 12:36 ` Mimi Zohar
2018-03-19 14:42 ` Jarkko Sakkinen
2018-03-06 11:37 ` Jarkko Sakkinen
2018-03-06 15:44 ` Jason Gunthorpe
2018-03-08 21:47 ` J Freyensee
2018-03-10 13:11 ` Jarkko Sakkinen [this message]
2018-03-05 16:56 ` [PATCH v3 4/5] tpm: migrate tpm2_get_tpm_pt() " Jarkko Sakkinen
2018-03-05 16:56 ` [PATCH v3 5/5] tpm: migrate tpm2_get_random() " Jarkko Sakkinen
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=1afb789425c50f06efbd80bc7377731fd1269d42.camel@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=why2jjj.linux@gmail.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).