From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.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 16:26:17 +0100 [thread overview]
Message-ID: <51530F99.8010405@redhat.com> (raw)
In-Reply-To: <5152E454.8060408@linux.vnet.ibm.com>
Il 27/03/2013 13:21, Stefan Berger ha scritto:
>
> 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?
Uff, we're really bad at consistent naming. :)
Given the above, I guess backends/tpm.c is fine. Then let's do the
following:
include/tpm/tpm.h -> include/sysemu/tpm.h
include/qemu/rng.h -> include/backends/rng.h
your new include -> include/backends/tpm.h
> My intention was to have tpm_passthrough moved into backends/.
I'm not sure that is the right thing to do since tpm_passthrough has
dependencies on DeviceState. It is not a pure backend, and if I
understand correctly it would likely not work with other TPM front-ends
than tpm_tis.c
> There's a file tpm/tpm_backend.c -- you want me to rename this one even
> though its located in a different directory?
tpm_backend.c and tpm_backend.h seem misnamed to begin with, so that
would be a separate but welcome change.
> Since I am not running a git repository any move/rename would be a
> deletion of a file plus its addition.
I don't understand.
Paolo
next prev parent reply other threads:[~2013-03-27 15:26 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
2013-03-27 15:26 ` Paolo Bonzini [this message]
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=51530F99.8010405@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=coreyb@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.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).