From: Ian Campbell <ian.campbell@citrix.com>
To: "Xu, Quan" <quan.xu@intel.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Olaf Hering <olaf@aepfle.de>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: stubdom vtpm build failure in staging
Date: Wed, 25 Feb 2015 13:54:19 +0000 [thread overview]
Message-ID: <1424872459.20243.116.camel@citrix.com> (raw)
In-Reply-To: <945CA011AD5F084CBEA3E851C0AB28890E895E94@SHSMSX101.ccr.corp.intel.com>
On Fri, 2015-02-13 at 02:07 +0000, Xu, Quan wrote:
> I try to redefine tpm2_types.h, deleting 'UINT16, UINT32 ..' and changing 'TPM_HANDLE ...' to ' TPM2_HANDLE ..',
> Or, could you give some advice? Thanks.
Perhaps make stubdom/vtpmmgr/types.h with these and use it for both?
Or switch to the standard uint.._t types in that whole subtree, but
perhaps some of this code is important from elsewhere in which case I
can see why you wouldn't want to do that.
Ian.
next prev parent reply other threads:[~2015-02-25 13:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 15:08 stubdom vtpm build failure in staging Olaf Hering
2015-01-28 15:13 ` Xu, Quan
2015-02-11 15:20 ` Olaf Hering
2015-02-12 16:56 ` Xu, Quan
2015-02-12 17:24 ` Xu, Quan
2015-02-12 17:40 ` Andrew Cooper
2015-02-13 2:07 ` Xu, Quan
2015-02-25 13:54 ` Ian Campbell [this message]
2015-02-27 15:07 ` Xu, Quan
2015-03-11 10:51 ` Ian Campbell
2015-03-12 1:46 ` Xu, Quan
2015-03-12 9:42 ` Ian Campbell
2015-03-12 15:44 ` Xu, Quan
2015-03-13 13:30 ` Olaf Hering
2015-03-13 15:39 ` Xu, Quan
2015-01-28 15:24 ` Ian Campbell
2015-01-29 7:34 ` Xu, Quan
2015-01-29 8:27 ` Olaf Hering
2015-01-29 9:22 ` Xu, Quan
2015-01-29 9:36 ` Olaf Hering
2015-01-29 10:27 ` Olaf Hering
2015-01-29 10:46 ` Ian Campbell
2015-01-30 8:09 ` Olaf Hering
2015-01-30 10:39 ` Ian Campbell
2015-01-30 11:03 ` Jan Beulich
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=1424872459.20243.116.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=olaf@aepfle.de \
--cc=quan.xu@intel.com \
--cc=xen-devel@lists.xen.org \
/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.