From: Peter Maydell <peter.maydell@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, Thomas Huth <thuth@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Jagannathan Raman <jag.raman@oracle.com>,
Elena Ufimtseva <elena.ufimtseva@oracle.com>,
John G Johnson <john.g.johnson@oracle.com>
Subject: Re: [PATCH] hw/remote/proxy: Remove dubious 'event_notifier-posix.c' include
Date: Tue, 6 Jun 2023 14:59:55 +0100 [thread overview]
Message-ID: <CAFEAcA-EgmjaMJkmiNF62Fqxu72V_UrFJj8Ae+21OL24S8GfQg@mail.gmail.com> (raw)
In-Reply-To: <20230606134913.93724-1-philmd@linaro.org>
On Tue, 6 Jun 2023 at 14:50, Philippe Mathieu-Daudé <philmd@linaro.org> wrote:
>
> event_notifier-posix.c is registered in meson's util_ss[] source
> set, which is built as libqemuutil.a.p library. Both tools and
> system emulation binaries are linked with qemuutil, so there is
> no point in including this source file.
>
> Introduced in commit bd36adb8df ("multi-process: create IOHUB
> object to handle irq").
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> Note, --enable-multiprocess doesn't seem to be covered in CI.
> ---
> hw/remote/proxy.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/hw/remote/proxy.c b/hw/remote/proxy.c
> index 1c7786b52c..2052d721e5 100644
> --- a/hw/remote/proxy.c
> +++ b/hw/remote/proxy.c
> @@ -22,7 +22,6 @@
> #include "qom/object.h"
> #include "qemu/event_notifier.h"
> #include "sysemu/kvm.h"
> -#include "util/event_notifier-posix.c"
Including one .c file from another is definitely very weird;
if it is by some chance not incorrect then it needs a big
comment describing why it's necessary...
-- PMM
next prev parent reply other threads:[~2023-06-06 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 13:49 [PATCH] hw/remote/proxy: Remove dubious 'event_notifier-posix.c' include Philippe Mathieu-Daudé
2023-06-06 13:59 ` Paolo Bonzini
2023-06-06 13:59 ` Peter Maydell [this message]
2023-06-06 14:07 ` Philippe Mathieu-Daudé
2023-06-06 14:19 ` Thomas Huth
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=CAFEAcA-EgmjaMJkmiNF62Fqxu72V_UrFJj8Ae+21OL24S8GfQg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=elena.ufimtseva@oracle.com \
--cc=jag.raman@oracle.com \
--cc=john.g.johnson@oracle.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).