From: "Michael S. Tsirkin" <mst@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, eblake@redhat.com,
marcandre.lureau@redhat.com, pbonzini@redhat.com,
berrange@redhat.com, arei.gonglei@huawei.com,
pizhenwei@bytedance.com, jonathan.cameron@huawei.com,
fan.ni@samsung.com, marcel.apfelbaum@gmail.com, jiri@resnulli.us,
jsnow@redhat.com, "Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v2 5/8] qapi/pci: Supply missing member documentation
Date: Wed, 11 Sep 2024 07:29:45 -0400 [thread overview]
Message-ID: <20240911072927-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240911112545.2248881-6-armbru@redhat.com>
On Wed, Sep 11, 2024 at 01:25:42PM +0200, Markus Armbruster wrote:
> Since we neglect to document a member of PciMemoryRegion, its
> description in the QEMU QMP Reference manual is "Not documented". Fix
> that.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
can you merge this?
> ---
> qapi/pci.json | 2 ++
> qapi/pragma.json | 1 -
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/qapi/pci.json b/qapi/pci.json
> index 78bee57b77..dc85a41d28 100644
> --- a/qapi/pci.json
> +++ b/qapi/pci.json
> @@ -33,6 +33,8 @@
> # - 'io' if the region is a PIO region
> # - 'memory' if the region is a MMIO region
> #
> +# @address: memory address
> +#
> # @size: memory size
> #
> # @prefetch: if @type is 'memory', true if the memory is prefetchable
> diff --git a/qapi/pragma.json b/qapi/pragma.json
> index 7b0e12f42b..baeae5bf52 100644
> --- a/qapi/pragma.json
> +++ b/qapi/pragma.json
> @@ -62,7 +62,6 @@
> 'MemoryDeviceInfoKind',
> 'NetClientDriver',
> 'ObjectType',
> - 'PciMemoryRegion',
> 'QCryptodevBackendServiceType',
> 'QKeyCode',
> 'RbdAuthMode',
> --
> 2.46.0
next prev parent reply other threads:[~2024-09-11 11:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 11:25 [PATCH v2 0/8] qapi: Supply some of the missing member documentation Markus Armbruster
2024-09-11 11:25 ` [PATCH v2 1/8] qapi/char: Supply " Markus Armbruster
2024-09-11 11:25 ` [PATCH v2 2/8] qapi/common: " Markus Armbruster
2024-09-11 11:25 ` [PATCH v2 3/8] qapi/crypto: " Markus Armbruster
2024-09-11 11:25 ` [PATCH v2 4/8] qapi/introspect: " Markus Armbruster
2024-09-11 11:25 ` [PATCH v2 5/8] qapi/pci: " Markus Armbruster
2024-09-11 11:29 ` Michael S. Tsirkin [this message]
2024-09-11 13:04 ` Markus Armbruster
2024-09-11 11:25 ` [PATCH v2 6/8] qapi/rocker: " Markus Armbruster
2024-09-11 11:25 ` [PATCH v2 7/8] qapi/cxl: " Markus Armbruster
2024-09-11 11:25 ` [PATCH v2 8/8] qapi: Document QCryptodevBackendServiceType Markus Armbruster
2024-09-13 8:09 ` [PATCH v2 0/8] qapi: Supply some of the missing member documentation Markus Armbruster
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=20240911072927-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=fan.ni@samsung.com \
--cc=jiri@resnulli.us \
--cc=jonathan.cameron@huawei.com \
--cc=jsnow@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=pizhenwei@bytedance.com \
--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).