All of lore.kernel.org
 help / color / mirror / Atom feed
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 1/5] tpm: rename tpm_chip_find_get() to tpm_find_get_ops()
Date: Tue, 26 Jun 2018 16:21:40 +0300	[thread overview]
Message-ID: <0084b7ca7e5b9a48f4f8354805eed8b3c44f90c3.camel@linux.intel.com> (raw)
In-Reply-To: <55a1a67f9c53ad8cac6e560bb23b1b712fdd4caa.camel@linux.intel.com>

On Tue, 2018-06-26 at 16:18 +0300, Jarkko Sakkinen wrote:
> On Tue, 2018-06-26 at 07:06 -0400, Stefan Berger wrote:
> > Rename tpm_chip_find_get() to tpm_find_get_ops() to more closely match
> > the tpm_put_ops() counter part.
> > 
> > Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
> 
> Awesome, makes sense by itself alone. Thanks Stefan. If we need
> follow up versions, no need to include this patch. I would take
> it even if the whole patch set was discarded for whatever reason.
> 
> Tested-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>

Already pushed to my master. Kind of waiting James to rebase his
tree before moving stuff to next.

/Jarkko

WARNING: multiple messages have this Message-ID (diff)
From: jarkko.sakkinen@linux.intel.com (Jarkko Sakkinen)
To: linux-security-module@vger.kernel.org
Subject: [PATCH v5 1/5] tpm: rename tpm_chip_find_get() to tpm_find_get_ops()
Date: Tue, 26 Jun 2018 16:21:40 +0300	[thread overview]
Message-ID: <0084b7ca7e5b9a48f4f8354805eed8b3c44f90c3.camel@linux.intel.com> (raw)
In-Reply-To: <55a1a67f9c53ad8cac6e560bb23b1b712fdd4caa.camel@linux.intel.com>

On Tue, 2018-06-26 at 16:18 +0300, Jarkko Sakkinen wrote:
> On Tue, 2018-06-26 at 07:06 -0400, Stefan Berger wrote:
> > Rename tpm_chip_find_get() to tpm_find_get_ops() to more closely match
> > the tpm_put_ops() counter part.
> > 
> > Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
> 
> Awesome, makes sense by itself alone. Thanks Stefan. If we need
> follow up versions, no need to include this patch. I would take
> it even if the whole patch set was discarded for whatever reason.
> 
> Tested-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>

Already pushed to my master. Kind of waiting James to rebase his
tree before moving stuff to next.

/Jarkko
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2018-06-26 13:21 UTC|newest]

Thread overview: 24+ 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 ` 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 11:06   ` Stefan Berger
2018-06-26 13:18   ` Jarkko Sakkinen
2018-06-26 13:18     ` Jarkko Sakkinen
2018-06-26 13:21     ` Jarkko Sakkinen [this message]
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 11:06   ` Stefan Berger
2018-06-26 13:22   ` Jarkko Sakkinen
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 11:06   ` Stefan Berger
2018-06-26 13:24   ` Jarkko Sakkinen
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 11:06   ` Stefan Berger
2018-06-26 13:25   ` Jarkko Sakkinen
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 11:06   ` Stefan Berger
2018-06-26 13:26   ` Jarkko Sakkinen
2018-06-26 13:26     ` 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=0084b7ca7e5b9a48f4f8354805eed8b3c44f90c3.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.