public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com>
To: Rajiv Andrade <srajiv@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	jmorris@namei.org, dave@linux.vnet.ibm.com, matthltc@us.ibm.com,
	zohar@linux.vnet.ibm.com, Mimi Zohar <zohar@us.ibm.com>
Subject: Re: [PATCH 2/2] TPM: integrity interface
Date: Mon, 2 Feb 2009 23:46:33 -0600	[thread overview]
Message-ID: <20090203054633.GA20589@hallyn.com> (raw)
In-Reply-To: <324e291aaf0c34062f2bca31da95a9f172ae2c28.1233592746.git.srajiv@linux.vnet.ibm.com>

Quoting Rajiv Andrade (srajiv@linux.vnet.ibm.com):
> This patch adds internal kernel support for:
>  - reading/extending a pcr value
>  - looking up the tpm_chip for a given chip number
> 
> Signed-off-by: Rajiv Andrade <srajiv@linux.vnet.ibm.com>
> Signed-off-by: Mimi Zohar <zohar@us.ibm.com>

This looks pretty nice, and though it's been awhile since
I've looked at this, the locking looks good too.

Acked-by: Serge Hallyn <serue@us.ibm.com>

  reply	other threads:[~2009-02-03  5:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 17:23 [PATCH 0/2] TPM: refactoring and integrity Rajiv Andrade
2009-02-02 17:23 ` [PATCH 1/2] TPM: sysfs functions consolidation Rajiv Andrade
2009-02-02 17:23 ` [PATCH 2/2] TPM: integrity interface Rajiv Andrade
2009-02-03  5:46   ` Serge E. Hallyn [this message]
2009-02-02 22:47 ` [PATCH 0/2] TPM: refactoring and integrity James Morris
2009-02-03  0:26 ` James Morris
  -- strict thread matches above, loose matches on Subject: below --
2009-01-29 23:01 Rajiv Andrade
2009-01-29 23:01 ` [PATCH 1/2] TPM: sysfs functions consolidation Rajiv Andrade
2009-01-29 23:01   ` [PATCH 2/2] TPM: integrity interface Rajiv Andrade

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=20090203054633.GA20589@hallyn.com \
    --to=serge@hallyn.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave@linux.vnet.ibm.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthltc@us.ibm.com \
    --cc=srajiv@linux.vnet.ibm.com \
    --cc=zohar@linux.vnet.ibm.com \
    --cc=zohar@us.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