All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org, "Eric Blake" <eblake@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH] qapi: convert intro sections fixup
Date: Thu, 08 Oct 2026 06:31:21 +0200	[thread overview]
Message-ID: <878q487qzq.fsf@pond.sub.org> (raw)
In-Reply-To: <CAFn=p-Yoa5pEgVAj_BqiBeACppadzgBBgVTUtq0EquOoWc6u8w@mail.gmail.com> (John Snow's message of "Wed, 7 Oct 2026 14:54:39 -0400")

John Snow <jsnow@redhat.com> writes:

> On Wed, Sep 30, 2026 at 1:39 AM Markus Armbruster <armbru@redhat.com> wrote:
>>
>> John Snow <jsnow@redhat.com> writes:
>>
>> > "We" (Me, I, Myself) missed two last spots during bulk conversion of the
>> > intro section syntax.
>> >
>> > Some definitions are still intentionally left without an intro
>> > section: BlockdevSnapshotSync is the only case I am presently aware
>> > of.
>>
>> There are quite a few more, but BlockdevSnapshotSync is the only one
>> followed by a plain section.
>>
>> > The remaining two were genuinely just missed; convert them now.
>> >
>> > Reported-by: Markus Armbruster <armbru@redhat.com>
>> > Signed-off-by: John Snow <jsnow@redhat.com>
>> > ---
>> >  qapi/machine-s390x.json |  4 ++--
>> >  qapi/qom.json           | 14 +++++++-------
>> >  2 files changed, 9 insertions(+), 9 deletions(-)
>> >
>> > diff --git a/qapi/machine-s390x.json b/qapi/machine-s390x.json
>> > index 8d8cbe2fb75..9ae559bbc2d 100644
>> > --- a/qapi/machine-s390x.json
>> > +++ b/qapi/machine-s390x.json
>> > @@ -150,8 +150,8 @@
>> >
>> >  ##
>> >  # @DummyBootCertificates:
>> > -#
>> > -# Not used by QMP; hack to let us use BootCertificatesList internally.
>> > +#     Not used by QMP; hack to let us use BootCertificatesList
>> > +#     internally.
>> >  #
>> >  # Since: 11.2
>> >  ##
>> > diff --git a/qapi/qom.json b/qapi/qom.json
>> > index e03ede34421..2d0d0e47fbb 100644
>> > --- a/qapi/qom.json
>> > +++ b/qapi/qom.json
>> > @@ -1039,13 +1039,13 @@
>> >
>> >  ##
>> >  # @SevSnpGuestProperties:
>> > -#
>> > -# Properties for sev-snp-guest objects.  Most of these are direct
>> > -# arguments for the KVM_SNP_* interfaces documented in the Linux
>> > -# kernel source under
>> > -# Documentation/arch/x86/amd-memory-encryption.rst, which are in turn
>> > -# closely coupled with the SNP_INIT/SNP_LAUNCH_* firmware commands
>> > -# documented in the SEV-SNP Firmware ABI Specification (Rev 0.9).
>> > +#     Properties for sev-snp-guest objects.  Most of these are direct
>> > +#     arguments for the KVM_SNP_* interfaces documented in the Linux
>> > +#     kernel source under
>> > +#     Documentation/arch/x86/amd-memory-encryption.rst, which are in
>> > +#     turn closely coupled with the SNP_INIT/SNP_LAUNCH_* firmware
>> > +#     commands documented in the SEV-SNP Firmware ABI Specification
>> > +#     (Rev 0.9).
>> >  #
>> >  # More usage information is also available in the QEMU source tree
>> >  # under docs/amd-memory-encryption.
>>
>> Hmm, shouldn't we split this one?
>
> Looping back to stuff that got missed:
>
> Split how? I think I have to rephrase this a bit, because when it gets
> inlined, it (might) be lacking the context of what specifically it
> refers to, i.e. "Most of these" might become ambiguous.

Yes.

Could s/these/the properties/ suffice for now?

  ##
  # @SevSnpGuestProperties:
  #     Properties for sev-snp-guest objects.
  #
  #     Most of the properties are direct arguments for the KVM_SNP_*
  #     interfaces documented in the Linux kernel source under
  #     Documentation/arch/x86/amd-memory-encryption.rst, which are in
  #     turn closely coupled with the SNP_INIT/SNP_LAUNCH_* firmware
  #     commands documented in the SEV-SNP Firmware ABI Specification
  #     (Rev 0.9).



      reply	other threads:[~2026-10-08  4:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 22:30 [PATCH] qapi: convert intro sections fixup John Snow
2026-09-30  5:39 ` Markus Armbruster
2026-09-30 14:07   ` John Snow
2026-10-07 18:54   ` John Snow
2026-10-08  4:31     ` Markus Armbruster [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=878q487qzq.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.