From: Andi Kleen <andi@firstfloor.org>
To: James Morris <jmorris@namei.org>
Cc: Joseph Cihula <joseph.cihula@intel.com>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, arjan@linux.intel.com,
hpa@zytor.com, andi@firstfloor.org,
Chris Wright <chrisw@sous-sol.org>,
jbeulich@novell.com, peterm@redhat.com, gang.wei@intel.com,
shane.wang@intel.com
Subject: Re: [RFC v4][PATCH 2/2] intel_txt: Intel(R) TXT and tboot kernel support
Date: Fri, 12 Jun 2009 12:23:20 +0200 [thread overview]
Message-ID: <20090612102320.GI25568@one.firstfloor.org> (raw)
In-Reply-To: <alpine.LRH.2.00.0906121509001.14633@tundra.namei.org>
On Fri, Jun 12, 2009 at 03:12:59PM +1000, James Morris wrote:
> On Fri, 5 Jun 2009, Joseph Cihula wrote:
>
> > Linux support for Intel(R) Trusted Execution Technology.
>
> > Signed-off-by: Joseph Cihula <joseph.cihula@intel.com>
> > Signed-off-by: Shane Wang <shane.wang@intel.com>
> > Signed-off-by: Gang Wei <gang.wei@intel.com>
>
> Reviewed-by: James Morris <jmorris@namei.org>
The earlier version was also reviewed by me and I think Joe addressed
all my concerns.
So it's
Reviewed-by: Andi Kleen <ak@linux.intel.com>
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-06-12 10:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 21:38 [RFC v4][PATCH 2/2] intel_txt: Intel(R) TXT and tboot kernel support Joseph Cihula
2009-06-12 5:12 ` James Morris
2009-06-12 10:23 ` Andi Kleen [this message]
2009-06-19 15:05 ` Pavel Machek
2009-06-19 17:52 ` Valdis.Kletnieks
2009-06-19 19:11 ` Alan Cox
2009-06-19 20:27 ` Alan Cox
2009-06-22 1:33 ` James Morris
2009-06-19 21:22 ` Pavel Machek
2009-06-19 18:34 ` Chris Wright
2009-06-22 1:54 ` James Morris
2009-06-26 21:30 ` Pavel Machek
2009-06-28 22:46 ` James Morris
2009-08-24 9:43 ` Pavel Machek
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=20090612102320.GI25568@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=arjan@linux.intel.com \
--cc=chrisw@sous-sol.org \
--cc=gang.wei@intel.com \
--cc=hpa@zytor.com \
--cc=jbeulich@novell.com \
--cc=jmorris@namei.org \
--cc=joseph.cihula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterm@redhat.com \
--cc=shane.wang@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 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.