From: "Philippe Mathieu-Daudé via" <qemu-devel@nongnu.org>
To: "Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philippe.mathieu.daude@gmail.com>
Cc: qemu-devel@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
qemu-trivial@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>
Subject: Re: [PATCH] qom/object: Remove circular include dependency
Date: Mon, 9 May 2022 14:44:43 +0200 [thread overview]
Message-ID: <47f863af-82f7-ec6e-a066-fec8509f34cd@amsat.org> (raw)
In-Reply-To: <CAFEAcA-tC5hUcYa7Q_GOe=7_k=De_yw0mm2F21ALh6-2D5ChzA@mail.gmail.com>
On 9/5/22 11:41, Peter Maydell wrote:
> On Mon, 9 May 2022 at 09:53, Philippe Mathieu-Daudé
> <philippe.mathieu.daude@gmail.com> wrote:
>>
>> From: Philippe Mathieu-Daudé <f4bug@amsat.org>
>>
>> "qom/object.h" doesn't need to include itself.
>>
>> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
>> ---
>> include/qom/object.h | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/include/qom/object.h b/include/qom/object.h
>> index 5f3d5b5bf5..ef7258a5e1 100644
>> --- a/include/qom/object.h
>> +++ b/include/qom/object.h
>> @@ -16,7 +16,6 @@
>>
>> #include "qapi/qapi-builtin-types.h"
>> #include "qemu/module.h"
>> -#include "qom/object.h"
>>
>> struct TypeImpl;
>> typedef struct TypeImpl *Type;
>
> Accidentally (but harmlessly)
This makes crash clang tools such clang-format, I'll amend that
to the description.
> added in commit db1015e92e0483 by a
> change generated by a script.
>
> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
>
> Eduardo: is it worth making ./scripts/codeconverter/converter.py
> handle this as a special case, so it doesn't add the include line
> to qom/object.h itself ? Or do we not really expect that script
> to be run on the codebase again in future ?
Oh, I see required_identifiers() adding this include in
scripts/codeconverter/codeconverter/qom_macros.py.
If we do not expect to use these scripts, we should remove it from
the repository. They are in good shape however, and might be still
valuable, so I'll amend a fix to the script.
Thanks for pointing at these scripts,
Phil.
next prev parent reply other threads:[~2022-05-09 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 8:46 [PATCH] qom/object: Remove circular include dependency Philippe Mathieu-Daudé
2022-05-09 9:36 ` Damien Hedde
2022-05-09 9:41 ` Peter Maydell
2022-05-09 12:44 ` Philippe Mathieu-Daudé via [this message]
2022-05-09 12:46 ` Peter Maydell
2022-05-09 9:52 ` Markus Armbruster
2022-06-28 8:54 ` Laurent Vivier
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=47f863af-82f7-ec6e-a066-fec8509f34cd@amsat.org \
--to=qemu-devel@nongnu.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eduardo@habkost.net \
--cc=f4bug@amsat.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philippe.mathieu.daude@gmail.com \
--cc=qemu-trivial@nongnu.org \
/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).