From: Stefan Berger <stefanb@linux.ibm.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: "Laurent Vivier" <lvivier@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [PATCH v2 01/11] docs/specs/tpm: Correct header path name
Date: Thu, 11 Jun 2020 12:19:38 -0400 [thread overview]
Message-ID: <4ed28a4c-8679-75d8-1078-9dbd0f38a8ca@linux.ibm.com> (raw)
In-Reply-To: <20200611160306.2751-2-philmd@redhat.com>
On 6/11/20 12:02 PM, Philippe Mathieu-Daudé wrote:
> Commit 8dc6701722 introduce the documentation but an
> incorrect path name was used. Fix that.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Stefan Berger <stefanb@linux.ibm.com>
> ---
> docs/specs/tpm.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/docs/specs/tpm.rst b/docs/specs/tpm.rst
> index 5e61238bc5..9e48e3b981 100644
> --- a/docs/specs/tpm.rst
> +++ b/docs/specs/tpm.rst
> @@ -199,8 +199,8 @@ to be used with the passthrough backend or the swtpm backend.
>
> QEMU files related to TPM backends:
> - ``backends/tpm.c``
> + - ``include/sysemu/tpm.h``
> - ``include/sysemu/tpm_backend.h``
> - - ``include/sysemu/tpm_backend_int.h``
>
> The QEMU TPM passthrough device
> -------------------------------
next prev parent reply other threads:[~2020-06-11 16:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 16:02 [PATCH v2 00/11] tpm: Split hw/ vs backends/ Philippe Mathieu-Daudé
2020-06-11 16:02 ` [PATCH v2 01/11] docs/specs/tpm: Correct header path name Philippe Mathieu-Daudé
2020-06-11 16:19 ` Stefan Berger [this message]
2020-06-11 16:02 ` [PATCH v2 02/11] backends: Add TPM files into their own directory Philippe Mathieu-Daudé
2020-06-11 16:20 ` Stefan Berger
2020-06-11 16:02 ` [PATCH v2 03/11] hw/tpm: Rename TPMDEV as TPM_BACKEND in Kconfig Philippe Mathieu-Daudé
2020-06-11 16:22 ` Stefan Berger
2020-06-11 16:02 ` [PATCH v2 04/11] hw/tpm: Do not include 'qemu/osdep.h' in header Philippe Mathieu-Daudé
2020-06-11 16:03 ` [PATCH v2 05/11] hw/tpm: Include missing 'qemu/option.h' header Philippe Mathieu-Daudé
2020-06-11 16:03 ` [PATCH v2 06/11] hw/tpm: Move 'hw/acpi/tpm.h' inclusion from header to sources Philippe Mathieu-Daudé
2020-06-11 16:03 ` [PATCH v2 07/11] hw/tpm: Remove unnecessary 'tpm_int.h' header inclusion Philippe Mathieu-Daudé
2020-06-11 16:03 ` [PATCH v2 08/11] hw/tpm: Move few declarations from 'tpm_util.h' to 'tpm_int.h' Philippe Mathieu-Daudé
2020-06-11 16:03 ` [PATCH v2 09/11] hw/tpm: Move DEFINE_PROP_TPMBE() macro to 'tmp_prop.h' local header Philippe Mathieu-Daudé
2020-06-11 16:03 ` [PATCH v2 10/11] hw/tpm: Make 'tpm_util.h' publicly accessible as "sysemu/tpm_util.h" Philippe Mathieu-Daudé
2020-06-11 16:03 ` [RFC PATCH v2 11/11] tpm: Move backend code under the 'backends/' directory Philippe Mathieu-Daudé
2020-06-11 16:21 ` [PATCH v2 00/11] tpm: Split hw/ vs backends/ Stefan Berger
2020-06-23 9:39 ` Paolo Bonzini
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=4ed28a4c-8679-75d8-1078-9dbd0f38a8ca@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).