From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: coreyb@linux.vnet.ibm.com,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
anthony@codemonkey.ws
Subject: Re: [Qemu-devel] [PATCH v2] QOM-ify the TPM support
Date: Wed, 27 Mar 2013 08:21:40 -0400 [thread overview]
Message-ID: <5152E454.8060408@linux.vnet.ibm.com> (raw)
In-Reply-To: <5152E0CF.7050300@redhat.com>
On 03/27/2013 08:06 AM, Paolo Bonzini wrote:
> Il 26/03/2013 17:28, Stefan Berger ha scritto:
>> QOM-ified the TPM support with much code borrowed from the rng implementation.
>>
>> What's missing may be that the tpm/tpm_passthrough.c be moved into backends/ .
>>
>> Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
>>
>> ---
>> v1->v2:
>> - followed to git revision e769bdc26
>>
>> ---
>> backends/Makefile.objs | 2
>> backends/tpm.c | 154 ++++++++++++++++++++++++++++++++++++++++++++
>> include/qemu/tpm.h | 170 +++++++++++++++++++++++++++++++++++++++++++++++++
> I think these should be tpm_backend.[ch] (with the include file in
> include/tpm). Can you rename the existing files with that name first?
With the above file naming and directory placement I followed the pattern of
backends/rng.c
include/qemu/rng.h
So are you planning on having them renamed and moved as well?
My intention was to have tpm_passthrough moved into backends/.
There's a file tpm/tpm_backend.c -- you want me to rename this one even
though its located in a different directory?
Since I am not running a git repository any move/rename would be a
deletion of a file plus its addition.
Stefan
> Paolo
>
next prev parent reply other threads:[~2013-03-27 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 16:28 [Qemu-devel] [PATCH v2] QOM-ify the TPM support Stefan Berger
2013-03-27 12:06 ` Paolo Bonzini
2013-03-27 12:21 ` Stefan Berger [this message]
2013-03-27 15:26 ` Paolo Bonzini
2013-03-27 18:00 ` Stefan Berger
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=5152E454.8060408@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=coreyb@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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.