From: Kent Yoder <key@linux.vnet.ibm.com>
To: xiaoyan.zhang@intel.com
Cc: linux-kernel@vger.kernel.org, joseph.cihula@intel.com,
gang.wei@intel.com, tpmdd-devel@lists.sourceforge.net,
debora@linux.vnet.ibm.com, srajiv@linux.vnet.ibm.com,
m.selhorst@sirrix.com, shpedoikal@gmail.com,
linux-security-module@vger.kernel.org, james.l.morris@oracle.com,
hpa@zytor.com, linux-api@vger.kernel.org, yoder1@us.ibm.com
Subject: Re: [PATCH v5 0/2] Add PPI support in tpm driver
Date: Wed, 22 Aug 2012 16:41:30 -0500 [thread overview]
Message-ID: <20120822214130.GA13519@linux.vnet.ibm.com> (raw)
In-Reply-To: <1345632442-1458-1-git-send-email-xiaoyan.zhang@intel.com>
On Wed, Aug 22, 2012 at 06:47:20PM +0800, xiaoyan.zhang@intel.com wrote:
> From: Xiaoyan Zhang <xiaoyan.zhang@intel.com>
>
> The Physical Presence Interface enables the OS and the BIOS to cooperate to
> provide a simple and straightforward platform user experience for
> administering the TPM without sacrificing security.
Thanks Xiaoyan, I'm including this in my next pull request to James.
Kent
> Xiaoyan Zhang (2):
> Documentation: sysfs for Physical Presence Interface
> driver: add PPI support in tpm driver
>
> Documentation/ABI/testing/sysfs-driver-ppi | 70 +++++
> drivers/char/tpm/Makefile | 2 +-
> drivers/char/tpm/tpm.c | 5 +
> drivers/char/tpm/tpm.h | 9 +
> drivers/char/tpm/tpm_ppi.c | 460 ++++++++++++++++++++++++++++
> 5 files changed, 545 insertions(+), 1 deletions(-)
> create mode 100644 Documentation/ABI/testing/sysfs-driver-ppi
> create mode 100644 drivers/char/tpm/tpm_ppi.c
>
> --
> 1.7.7.6
>
prev parent reply other threads:[~2012-08-22 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 10:47 [PATCH v5 0/2] Add PPI support in tpm driver xiaoyan.zhang-ral2JQCrhuEAvxtiuMwx3w
2012-08-22 10:47 ` [PATCH v5 1/2] Documentation: sysfs for Physical Presence Interface xiaoyan.zhang
2012-08-22 10:47 ` [PATCH v5 2/2] driver: add PPI support in tpm driver xiaoyan.zhang
2012-08-22 21:41 ` Kent Yoder [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=20120822214130.GA13519@linux.vnet.ibm.com \
--to=key@linux.vnet.ibm.com \
--cc=debora@linux.vnet.ibm.com \
--cc=gang.wei@intel.com \
--cc=hpa@zytor.com \
--cc=james.l.morris@oracle.com \
--cc=joseph.cihula@intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=m.selhorst@sirrix.com \
--cc=shpedoikal@gmail.com \
--cc=srajiv@linux.vnet.ibm.com \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=xiaoyan.zhang@intel.com \
--cc=yoder1@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;
as well as URLs for NNTP newsgroup(s).