diff options
author | Marc-André Lureau <marcandre.lureau@redhat.com> | 2016-09-25 13:13:21 +0400 |
---|---|---|
committer | Markus Armbruster <armbru@redhat.com> | 2017-01-16 09:19:48 +0100 |
commit | 0ea87df5064a3f02de564fca06234e0b240368ee (patch) | |
tree | 96734a5963bc7d773f7cae39e58c9ea82033e3cb | |
parent | adcbc0d99780af87ad3ffe99b92e0e64fb4cb73c (diff) |
qmp-commands: remove device_add from txt
It's already fully described in the schema. Fix the schema to document
the command and not the argument (place doc before first arg).
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
-rw-r--r-- | docs/qmp-commands.txt | 26 |
1 files changed, 0 insertions, 26 deletions
diff --git a/docs/qmp-commands.txt b/docs/qmp-commands.txt index 89170aabde..07138cdc8a 100644 --- a/docs/qmp-commands.txt +++ b/docs/qmp-commands.txt @@ -46,34 +46,8 @@ If you're planning to adopt QMP, please observe the following: 3. Errors, in special, are not documented. Applications should NOT check for specific errors classes or data (it's strongly recommended to only check for the "error" key) - 2. Regular Commands =================== Server's responses in the examples below are always a success response, please refer to the QMP specification for more details on error responses. - -device_add ----------- - -Add a device. - -Arguments: - -- "driver": the name of the new device's driver (json-string) -- "bus": the device's parent bus (device tree path, json-string, optional) -- "id": the device's ID, must be unique (json-string) -- device properties - -Example: - --> { "execute": "device_add", "arguments": { "driver": "e1000", "id": "net1" } } -<- { "return": {} } - -Notes: - -(1) For detailed information about this command, please refer to the - 'docs/qdev-device-use.txt' file. - -(2) It's possible to list device properties by running QEMU with the - "-device DEVICE,\?" command-line argument, where DEVICE is the device's name |