From: Olaf Hering <olaf@aepfle.de>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] tools/vtpm: do not install if vtpm can not be build
Date: Tue, 3 Apr 2012 17:01:46 +0200 [thread overview]
Message-ID: <20120403150146.GA8190@aepfle.de> (raw)
In-Reply-To: <20347.3980.401034.775731@mariner.uk.xensource.com>
On Tue, Apr 03, Ian Jackson wrote:
> But my second comment is: shouldn't this kind of test be done with
> autoconf nowadays ?
Yes, that was my thinking as well after poking around some more in the
vtpm subdirectory. The header check for example can be done with
autoconf.
Since I more or less enabled vtpm by accident, and currently lack the
time to get this in shape for the 4.2 release, please drop this patch.
I will look at this later.
Olaf
prev parent reply other threads:[~2012-04-03 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 19:02 [PATCH] tools/vtpm: do not install if vtpm can not be build Olaf Hering
2012-04-03 14:56 ` Ian Jackson
2012-04-03 15:01 ` Olaf Hering [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=20120403150146.GA8190@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).