linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Kent Yoder <key@linux.vnet.ibm.com>
Cc: Peter.Huewe@infineon.com, linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	tpmdd-devel@lists.sourceforge.net, adlai@linux.vnet.ibm.com,
	xiaoyan.zhang@intel.com, jj@chaosbits.net, hpa@zytor.com
Subject: Re: [GIT PULL] tpmdd: TPM drivers, tpm-rng and fixes
Date: Tue, 28 Aug 2012 07:58:39 +1000 (EST)	[thread overview]
Message-ID: <alpine.LRH.2.02.1208280757340.18678@tundra.namei.org> (raw)
In-Reply-To: <alpine.LRH.2.02.1208280627360.18515@tundra.namei.org>

On Tue, 28 Aug 2012, James Morris wrote:

> On Mon, 27 Aug 2012, Kent Yoder wrote:
> 
> > > I may have missed something, but what do you mean by pullreq patches?
> > 
> >   Just the stuff I asked you to pull here.
> 
> Looks like it could be an issue with the development repo I have on my 
> laptop while traveling.  Investigating...

Confirmed, but all is fixed now and I've pulled the patches.

Thanks.


-- 
James Morris
<jmorris@namei.org>

  reply	other threads:[~2012-08-27 22:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 21:52 [GIT PULL] tpmdd: TPM drivers, tpm-rng and fixes Kent Yoder
2012-08-22 23:42 ` Jeff Garzik
2012-08-23 20:32 ` James Morris
2012-08-24  7:27   ` Peter.Huewe
2012-08-24  8:32   ` Peter.Huewe
2012-08-24 15:05     ` Kent Yoder
2012-08-24 22:02       ` James Morris
2012-08-27  7:23         ` Peter.Huewe
2012-08-27 16:17           ` Kent Yoder
2012-08-27 17:21             ` James Morris
2012-08-27 18:02               ` Kent Yoder
2012-08-27 20:28                 ` James Morris
2012-08-27 21:58                   ` James Morris [this message]
2012-08-27 17:19           ` James Morris

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=alpine.LRH.2.02.1208280757340.18678@tundra.namei.org \
    --to=jmorris@namei.org \
    --cc=Peter.Huewe@infineon.com \
    --cc=adlai@linux.vnet.ibm.com \
    --cc=hpa@zytor.com \
    --cc=jj@chaosbits.net \
    --cc=key@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=tpmdd-devel@lists.sourceforge.net \
    --cc=xiaoyan.zhang@intel.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).