qapi: Reorder doc comments for future doc generator
The doc generator we're going to add expects a fairly rigid doc comment structure. Reorder / rephrase some doc comments to please it. Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Message-Id: <20170113144135.5150-8-marcandre.lureau@redhat.com> Reviewed-by: Markus Armbruster <armbru@redhat.com> [Commit message rewritten] Signed-off-by: Markus Armbruster <armbru@redhat.com>
This commit is contained in:
parent
ae4dbed0fe
commit
5807ff88b1
@ -4739,17 +4739,17 @@
|
||||
# it should be passed by management with device_add command when
|
||||
# a CPU is being hotplugged.
|
||||
#
|
||||
# @node-id: #optional NUMA node ID the CPU belongs to
|
||||
# @socket-id: #optional socket number within node/board the CPU belongs to
|
||||
# @core-id: #optional core number within socket the CPU belongs to
|
||||
# @thread-id: #optional thread number within core the CPU belongs to
|
||||
#
|
||||
# Note: currently there are 4 properties that could be present
|
||||
# but management should be prepared to pass through other
|
||||
# properties with device_add command to allow for future
|
||||
# interface extension. This also requires the filed names to be kept in
|
||||
# sync with the properties passed to -device/device_add.
|
||||
#
|
||||
# @node-id: #optional NUMA node ID the CPU belongs to
|
||||
# @socket-id: #optional socket number within node/board the CPU belongs to
|
||||
# @core-id: #optional core number within socket the CPU belongs to
|
||||
# @thread-id: #optional thread number within core the CPU belongs to
|
||||
#
|
||||
# Since: 2.7
|
||||
##
|
||||
{ 'struct': 'CpuInstanceProperties',
|
||||
|
@ -272,9 +272,9 @@
|
||||
#
|
||||
# Emitted when guest executes ACPI _OST method.
|
||||
#
|
||||
# Since: 2.1
|
||||
#
|
||||
# @info: ACPIOSTInfo type as described in qapi-schema.json
|
||||
#
|
||||
# Since: 2.1
|
||||
##
|
||||
{ 'event': 'ACPI_DEVICE_OST',
|
||||
'data': { 'info': 'ACPIOSTInfo' } }
|
||||
|
@ -78,14 +78,13 @@
|
||||
# @SchemaInfo:
|
||||
#
|
||||
# @name: the entity's name, inherited from @base.
|
||||
# The SchemaInfo is always referenced by this name.
|
||||
# Commands and events have the name defined in the QAPI schema.
|
||||
# Unlike command and event names, type names are not part of
|
||||
# the wire ABI. Consequently, type names are meaningless
|
||||
# strings here, although they are still guaranteed unique
|
||||
# regardless of @meta-type.
|
||||
#
|
||||
# All references to other SchemaInfo are by name.
|
||||
#
|
||||
# @meta-type: the entity's meta type, inherited from @base.
|
||||
#
|
||||
# Additional members depend on the value of @meta-type.
|
||||
|
Loading…
Reference in New Issue
Block a user