From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Kashyap Chamarthy" <kchamart@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v3 1/3] docs/interop/firmware.json: add new enum FirmwareFormat
Date: Mon, 11 Mar 2024 13:08:19 +0100 [thread overview]
Message-ID: <b04ef6ef-1e1b-49d6-9184-16474ad32dc5@linaro.org> (raw)
In-Reply-To: <20240311-qapi-firmware-json-v3-1-ceea6e35eb4a@linutronix.de>
On 11/3/24 12:46, Thomas Weißschuh wrote:
> Only a small subset of all blockdev drivers make sense for firmware
> images. Introduce and use a new enum to represent this.
>
> This also reduces the dependency of firmware.json on the global qapi
> definitions.
>
> Suggested-by: Daniel P. Berrangé <berrange@redhat.com>
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> ---
> docs/interop/firmware.json | 18 ++++++++++++++++--
> 1 file changed, 16 insertions(+), 2 deletions(-)
> +##
> +# @FirmwareFormat:
> +#
> +# Formats that are supported for firmware images.
> +#
> +# Since: 8.3
That will be 9.0 :/
> +##
> +{ 'enum': 'FirmwareFormat',
> + 'data': [ 'raw', 'qcow2' ] }
next prev parent reply other threads:[~2024-03-11 12:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 11:46 [PATCH v3 0/3] docs/interop/firmware.json: scripts/qapi-gen.py compatibility Thomas Weißschuh
2024-03-11 11:46 ` [PATCH v3 1/3] docs/interop/firmware.json: add new enum FirmwareFormat Thomas Weißschuh
2024-03-11 12:08 ` Philippe Mathieu-Daudé [this message]
2024-03-11 12:53 ` Thomas Weißschuh
2024-03-11 13:29 ` Markus Armbruster
2024-03-28 10:31 ` Thomas Weißschuh
2024-03-11 11:46 ` [PATCH v3 2/3] docs/interop/firmware.json: add new enum FirmwareArchitecture Thomas Weißschuh
2024-03-11 13:33 ` Markus Armbruster
2024-03-11 11:47 ` [PATCH v3 3/3] docs: add test for firmware.json QAPI Thomas Weißschuh
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=b04ef6ef-1e1b-49d6-9184-16474ad32dc5@linaro.org \
--to=philmd@linaro.org \
--cc=berrange@redhat.com \
--cc=kchamart@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thomas.weissschuh@linutronix.de \
/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).