Linux CXL
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@redhat.com>
To: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Cc: "Markus Armbruster" <armbru@redhat.com>,
	"Peter Xu" <peterx@redhat.com>, "Fabiano Rosas" <farosas@suse.de>,
	qemu-block@nongnu.org, "Eric Blake" <eblake@redhat.com>,
	"Alex Williamson" <alex@shazbot.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"Lukas Straub" <lukasstraub2@web.de>,
	"Philippe Mathieu-Daudé" <philmd@mailo.com>,
	"Zhao Liu" <zhao1.liu@intel.com>,
	"Hanna Reitz" <hreitz@redhat.com>,
	linux-cxl@vger.kernel.org, "Kevin Wolf" <kwolf@redhat.com>
Subject: Re: [PATCH 01/10] qapi: convert simple enum intros for vfio.json
Date: Wed, 9 Sep 2026 07:45:38 +0200	[thread overview]
Message-ID: <0bab1434-c36b-49e4-b902-b446b8be9617@redhat.com> (raw)
In-Reply-To: <20260909041640.69080-2-jsnow@redhat.com>

On 9/9/26 06:16, John Snow wrote:
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
>   qapi/vfio.json | 15 +++++++--------
>   1 file changed, 7 insertions(+), 8 deletions(-)
> 
> diff --git a/qapi/vfio.json b/qapi/vfio.json
> index 3d61fc38ecd..47fff8b979d 100644
> --- a/qapi/vfio.json
> +++ b/qapi/vfio.json
> @@ -10,14 +10,13 @@
>   
>   ##
>   # @QapiVfioMigrationState:
> -#
> -# An enumeration of the VFIO device migration states.  In addition to
> -# the regular states, there are prepare states (with 'prepare' suffix)
> -# which indicate that the device is just about to transition to the
> -# corresponding state.  Note that seeing a prepare state for state X
> -# doesn't guarantee that the next state will be X, as the state
> -# transition can fail and the device may transition to a different
> -# state instead.
> +#     An enumeration of the VFIO device migration states.  In addition
> +#     to the regular states, there are prepare states (with 'prepare'
> +#     suffix) which indicate that the device is just about to
> +#     transition to the corresponding state.  Note that seeing a
> +#     prepare state for state X doesn't guarantee that the next state
> +#     will be X, as the state transition can fail and the device may
> +#     transition to a different state instead.
>   #
>   # @stop: The device is stopped.
>   #

Reviewed-by: Cédric Le Goater <clg@redhat.com>

Thanks,

C.


  reply	other threads:[~2026-09-09  5:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09  4:16 [PATCH 00/10] qapi: convert simple enum intro sections John Snow
2026-09-09  4:16 ` [PATCH 01/10] qapi: convert simple enum intros for vfio.json John Snow
2026-09-09  5:45   ` Cédric Le Goater [this message]
2026-09-09  4:16 ` [PATCH 02/10] qapi: convert simple enum intros for machine-common.json John Snow
2026-09-09  4:16 ` [PATCH 03/10] qapi: convert simple enum intros for introspect.json John Snow
2026-09-09  4:16 ` [PATCH 04/10] qapi: convert simple enum intros for block.json John Snow
2026-09-09  4:16 ` [PATCH 05/10] qapi: convert simple enum intros for cypto.json John Snow
2026-09-10  4:47   ` Markus Armbruster
2026-09-09  4:16 ` [PATCH 06/10] qapi: convert simple enum intros for cxl.json John Snow
2026-09-09  4:16 ` [PATCH 07/10] qapi: convert simple enum intros for yank.json John Snow
2026-09-09  4:16 ` [PATCH 08/10] qapi: convert simple enum intros for migration.json John Snow
2026-09-09  4:16 ` [PATCH 09/10] qapi: convert simple enum intros for machine.json John Snow
2026-09-09  4:16 ` [PATCH 10/10] qapi: convert simple enum intros for block-core.json John Snow
2026-09-09  6:31 ` [PATCH 00/10] qapi: convert simple enum intro sections 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=0bab1434-c36b-49e4-b902-b446b8be9617@redhat.com \
    --to=clg@redhat.com \
    --cc=alex@shazbot.org \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=farosas@suse.de \
    --cc=hreitz@redhat.com \
    --cc=jic23@kernel.org \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=lukasstraub2@web.de \
    --cc=peterx@redhat.com \
    --cc=philmd@mailo.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=zhao1.liu@intel.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