From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>,
linux-integrity@vger.kernel.org, zohar@linux.vnet.ibm.com
Cc: jgg@ziepe.ca, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH v5 5/5] ima: Get rid of ima_used_chip and use ima_tpm_chip != NULL instead
Date: Tue, 26 Jun 2018 16:26:13 +0300 [thread overview]
Message-ID: <2bb4c098622cff2430d96f17c02b34fcef4d882e.camel@linux.intel.com> (raw)
In-Reply-To: <20180626110619.2362791-6-stefanb@linux.vnet.ibm.com>
On Tue, 2018-06-26 at 07:06 -0400, Stefan Berger wrote:
> Get rid of ima_used_chip and use ima_tpm_chip variable instead for
> determining whether to use the TPM chip.
>
> Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
Acked-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
(i.e. LGTM but no competence to give a detailed review).
/Jarkko
prev parent reply other threads:[~2018-06-26 13:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 11:06 [PATCH v5 0/5] Have IMA find and use a tpm_chip until system shutdown Stefan Berger
2018-06-26 11:06 ` [PATCH v5 1/5] tpm: rename tpm_chip_find_get() to tpm_find_get_ops() Stefan Berger
2018-06-26 13:18 ` Jarkko Sakkinen
2018-06-26 13:21 ` Jarkko Sakkinen
2018-06-26 11:06 ` [PATCH v5 2/5] tpm: Implement tpm_default_chip() to find a TPM chip Stefan Berger
2018-06-26 13:22 ` Jarkko Sakkinen
2018-06-26 11:06 ` [PATCH v5 3/5] tpm: Convert tpm_find_get_ops() to use tpm_default_chip() Stefan Berger
2018-06-26 13:24 ` Jarkko Sakkinen
2018-06-26 11:06 ` [PATCH v5 4/5] ima: Use tpm_default_chip() and call TPM functions with a tpm_chip Stefan Berger
2018-06-26 13:25 ` Jarkko Sakkinen
2018-06-26 11:06 ` [PATCH v5 5/5] ima: Get rid of ima_used_chip and use ima_tpm_chip != NULL instead Stefan Berger
2018-06-26 13:26 ` Jarkko Sakkinen [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=2bb4c098622cff2430d96f17c02b34fcef4d882e.camel@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=stefanb@linux.vnet.ibm.com \
--cc=zohar@linux.vnet.ibm.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).