From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: "Peter Hüwe" <PeterHuewe@gmx.de>
Cc: tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Ashley Lai <ashley@ashleylai.com>
Subject: Re: tpm: Remainder of earlier clean up
Date: Mon, 9 Dec 2013 18:33:09 -0700 [thread overview]
Message-ID: <20131210013309.GP5429@obsidianresearch.com> (raw)
In-Reply-To: <201312071421.43218.PeterHuewe@gmx.de>
On Sat, Dec 07, 2013 at 02:21:43PM +0100, Peter Hüwe wrote:
> Hi Jason
>
> did push everything to
> https://github.com/PeterHuewe/linux-tpmdd/tree/testing-and-review
> against latest rc, with alls signed-offs and reviewed-bys
>
> I'll move it to for-james after giving it a final test run.
Thanks!
Jason
prev parent reply other threads:[~2013-12-10 1:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 3:38 tpm: Remainder of earlier clean up Jason Gunthorpe
2013-11-04 3:38 ` [PATCH 1/5 v2] tpm: Pull everything related to /dev/tpmX into tpm-dev.c Jason Gunthorpe
2013-11-16 22:18 ` [tpmdd-devel] " Ashley Lai
2013-11-17 0:12 ` Jason Gunthorpe
2013-11-04 3:38 ` [PATCH 2/5 v2] tpm: Pull everything related to sysfs into tpm-sysfs.c Jason Gunthorpe
2013-11-16 23:53 ` [tpmdd-devel] " Ashley Lai
2013-11-17 0:24 ` Jason Gunthorpe
2013-11-04 3:38 ` [PATCH 3/5 v2] tpm: Create a tpm_class_ops structure and use it in the drivers Jason Gunthorpe
2013-11-17 0:57 ` [tpmdd-devel] " Ashley Lai
2013-11-04 3:38 ` [PATCH 4/5 v2] tpm: Use the ops structure instead of a copy in tpm_vendor_specific Jason Gunthorpe
2013-11-17 1:09 ` [tpmdd-devel] " Ashley Lai
2013-11-04 3:38 ` [PATCH 5/5 v2] tpm: Make tpm-dev allocate a per-file structure Jason Gunthorpe
2013-11-17 2:01 ` [tpmdd-devel] " Ashley Lai
2013-11-08 16:54 ` [tpmdd-devel] tpm: Remainder of earlier clean up Ashley Lai
2013-11-08 17:23 ` Aw: " Peter Huewe
2013-12-07 13:21 ` Peter Hüwe
2013-12-10 1:33 ` Jason Gunthorpe [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=20131210013309.GP5429@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=PeterHuewe@gmx.de \
--cc=ashley@ashleylai.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox