From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: Stefan Berger <stefanb@linux.vnet.ibm.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH-for-8.0 2/3] hw/intc: Move omap_lcdc.c out of target-specific source set
Date: Fri, 9 Dec 2022 18:44:34 +0100 [thread overview]
Message-ID: <f56fd611-578f-a17b-7026-c5a4d4455b25@linaro.org> (raw)
In-Reply-To: <6548f60f-1b98-f35e-e568-af9b2537fc2c@redhat.com>
On 9/12/22 18:21, Thomas Huth wrote:
> On 09/12/2022 18.00, Philippe Mathieu-Daudé wrote:
>> The Goldfish interrupt controller is not target specific.
>
> It's also only used by m68k which is only built once, so this does help
> reducing the compile time ... but I agree, it will be more helpful in
> the future the more code we move to softmmu_ss instead of specific_ss.
And soon MIPS too:
https://lore.kernel.org/qemu-devel/20221124212916.723490-4-jiaxun.yang@flygoat.com/
>> While the Exynos interrupt combiner is only used by the ARM
>> targets, we can build this device once for all.
>> >> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>> ---
>> hw/intc/meson.build | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
next prev parent reply other threads:[~2022-12-09 17:45 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é [this message]
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
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=f56fd611-578f-a17b-7026-c5a4d4455b25@linaro.org \
--to=philmd@linaro.org \
--cc=jiaxun.yang@flygoat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.com \
--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).