From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: Michael Roth <michael.roth@amd.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH-for-9.1?] qapi/util: Include missing 'qapi/error.h' header
Date: Wed, 7 Aug 2024 00:32:30 +1000 [thread overview]
Message-ID: <a37ece8a-3fcf-476c-a943-d48b1ace0337@linaro.org> (raw)
In-Reply-To: <20240806124138.90636-1-philmd@linaro.org>
On 8/6/24 22:41, Philippe Mathieu-Daudé wrote:
> qapi_enum_parse() uses the Error type which is
> declared in "qapi/error.h". Include "qapi/error.h"
> in order to avoid:
>
> include/qapi/util.h:27:30: error: unknown type name 'Error'
> int def, Error **errp);
> ^
>
> Note we include it after the QEnumLookup declaration
> to avoid:
>
> In file included from include/qapi/error.h:275:
> qapi/qapi-types-error.h:30:14: error: unknown type name 'QEnumLookup'
> extern const QEnumLookup QapiErrorClass_lookup;
> ^
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> include/qapi/util.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/qapi/util.h b/include/qapi/util.h
> index b8254247b8..568f31ac9e 100644
> --- a/include/qapi/util.h
> +++ b/include/qapi/util.h
> @@ -22,6 +22,8 @@ typedef struct QEnumLookup {
> const int size;
> } QEnumLookup;
>
> +#include "qapi/error.h"
> +
> const char *qapi_enum_lookup(const QEnumLookup *lookup, int val);
> int qapi_enum_parse(const QEnumLookup *lookup, const char *buf,
> int def, Error **errp);
Error is in qemu/typedefs.h, which is included from qemu/osdeps.h, which is always first.
There is should be no need for this patch. Why do you think it is needed?
r~
prev parent reply other threads:[~2024-08-06 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 12:41 [PATCH-for-9.1?] qapi/util: Include missing 'qapi/error.h' header Philippe Mathieu-Daudé
2024-08-06 14:32 ` Richard Henderson [this message]
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=a37ece8a-3fcf-476c-a943-d48b1ace0337@linaro.org \
--to=richard.henderson@linaro.org \
--cc=armbru@redhat.com \
--cc=michael.roth@amd.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@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).