From: Kent Yoder <key@linux.vnet.ibm.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: James Morris <jmorris@namei.org>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
tpmdd-devel@lists.sourceforge.net,
Peter Huewe <peter.huewe@infineon.com>,
Bryan Freed <bfreed@chromium.org>
Subject: Re: [GIT PULL] New TPM driver, hwrng driver and fixes
Date: Tue, 14 Aug 2012 11:37:15 -0500 [thread overview]
Message-ID: <20120814163715.GA1524@linux.vnet.ibm.com> (raw)
In-Reply-To: <5029671A.70402@zytor.com>
On Mon, Aug 13, 2012 at 01:44:10PM -0700, H. Peter Anvin wrote:
> On 07/27/2012 11:14 AM, Kent Yoder wrote:
> > Hi James,
> >
> > Please pull from this new branch and ignore the 7-25-12 branch. This
> > new branch includes fixes for comments by hpa. I've also included one
> > additional patch from [1] to close a race and prevent possibly sensitive
> > data from being free'd before being zeroed. I'm attaching this entire
> > diff here since my fixes for hpa's comments aren't public yet.
> >
> > Thanks,
> > Kent
> >
> > [1] https://lkml.org/lkml/2012/7/25/431
> >
>
> Hi guys,
>
> I was wondering what the status on this tree is?
Hi, I'm staging these patches against latest upstream and will be
hopefully adding another new driver and PPI patches from Intel on top,
to be included in a new pullreq for James.
Kent
>
> -hpa
>
prev parent reply other threads:[~2012-08-14 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 18:14 [GIT PULL] New TPM driver, hwrng driver and fixes Kent Yoder
2012-07-27 18:24 ` H. Peter Anvin
2012-07-27 19:36 ` Kent Yoder
2012-07-27 20:30 ` Kent Yoder
2012-07-27 22:09 ` H. Peter Anvin
2012-07-28 0:45 ` Kent Yoder
2012-07-30 20:51 ` Kent Yoder
2012-07-30 20:52 ` H. Peter Anvin
2012-08-13 20:44 ` H. Peter Anvin
2012-08-14 16:37 ` 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=20120814163715.GA1524@linux.vnet.ibm.com \
--to=key@linux.vnet.ibm.com \
--cc=bfreed@chromium.org \
--cc=hpa@zytor.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=peter.huewe@infineon.com \
--cc=tpmdd-devel@lists.sourceforge.net \
/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.