From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: Stefan Berger <stefanb@linux.vnet.ibm.com>
Subject: Re: [PATCH-for-8.0 3/3] hw/tpm: Move tpm_ppc.c out of target-specific source set
Date: Fri, 9 Dec 2022 18:14:14 +0100 [thread overview]
Message-ID: <9ce14b12-b993-58bc-bc63-d189b83692f0@redhat.com> (raw)
In-Reply-To: <20221209170042.71169-4-philmd@linaro.org>
On 09/12/2022 18.00, Philippe Mathieu-Daudé wrote:
> The TPM Physical Presence Interface is not target specific.
> Build this file once for all targets.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> hw/tpm/meson.build | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/tpm/meson.build b/hw/tpm/meson.build
> index 1c68d81d6a..3eacbe8c5d 100644
> --- a/hw/tpm/meson.build
> +++ b/hw/tpm/meson.build
> @@ -3,6 +3,6 @@ softmmu_ss.add(when: 'CONFIG_TPM_TIS_ISA', if_true: files('tpm_tis_isa.c'))
> softmmu_ss.add(when: 'CONFIG_TPM_TIS_SYSBUS', if_true: files('tpm_tis_sysbus.c'))
> softmmu_ss.add(when: 'CONFIG_TPM_CRB', if_true: files('tpm_crb.c'))
>
> -specific_ss.add(when: ['CONFIG_SOFTMMU', 'CONFIG_TPM_TIS'], if_true: files('tpm_ppi.c'))
> -specific_ss.add(when: ['CONFIG_SOFTMMU', 'CONFIG_TPM_CRB'], if_true: files('tpm_ppi.c'))
> +softmmu_ss.add(when: ['CONFIG_SOFTMMU', 'CONFIG_TPM_TIS'], if_true: files('tpm_ppi.c'))
> +softmmu_ss.add(when: ['CONFIG_SOFTMMU', 'CONFIG_TPM_CRB'], if_true: files('tpm_ppi.c'))
> specific_ss.add(when: 'CONFIG_TPM_SPAPR', if_true: files('tpm_spapr.c'))
Typo in the subject: ppc ==> ppi
Then, while you're at it: Why is it checking the CONFIG_SOFTMMU switch here,
too? I fail to see why this is necessary here, we never check this for other
files that we put into specific_ss or softmmu_ss.
Thomas
next prev parent reply other threads:[~2022-12-09 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 17:00 [PATCH-for-8.0 0/3] hw: Move few units out of the target-specific source set Philippe Mathieu-Daudé
2022-12-09 17:00 ` [PATCH-for-8.0 1/3] hw/display: Move omap_lcdc.c out of " Philippe Mathieu-Daudé
2022-12-09 17:00 ` [PATCH-for-8.0 2/3] hw/intc: " Philippe Mathieu-Daudé
2022-12-09 17:21 ` Thomas Huth
2022-12-09 17:44 ` Philippe Mathieu-Daudé
2022-12-10 15:01 ` Thomas Huth
2022-12-09 17:00 ` [PATCH-for-8.0 3/3] hw/tpm: Move tpm_ppc.c " Philippe Mathieu-Daudé
2022-12-09 17:14 ` Thomas Huth [this message]
2022-12-09 17:37 ` Philippe Mathieu-Daudé
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=9ce14b12-b993-58bc-bc63-d189b83692f0@redhat.com \
--to=thuth@redhat.com \
--cc=philmd@linaro.org \
--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).