diff options
| author | Lei Li <lilei@linux.vnet.ibm.com> | 2013-05-21 18:27:58 +0800 |
|---|---|---|
| committer | Anthony Liguori <aliguori@us.ibm.com> | 2013-05-22 07:40:10 -0500 |
| commit | 6a85e60cb994bd95d1537aafbff65816f3de4637 (patch) | |
| tree | ad8f2a4aaac0b06e381db29530612925a84316cc /qapi-schema.json | |
| parent | 17bf9735dd5a46d829cfb175703c6a2c254a9aa2 (diff) | |
| download | qemu-6a85e60cb994bd95d1537aafbff65816f3de4637.tar.gz qemu-6a85e60cb994bd95d1537aafbff65816f3de4637.tar.bz2 qemu-6a85e60cb994bd95d1537aafbff65816f3de4637.zip | |
chardev: Make the name of memory device consistent
Now we have memory char device, but the backend name of it
is a little confusion. We actually register it by 'memory', but
the description in qemu-option, the name of open functions
and the new api backend called it 'ringbuf'. It should keep
consistent. This patch named it all to 'memory'.
Signed-off-by: Lei Li <lilei@linux.vnet.ibm.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Message-id: 1369132079-11377-2-git-send-email-lilei@linux.vnet.ibm.com
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'qapi-schema.json')
| -rw-r--r-- | qapi-schema.json | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/qapi-schema.json b/qapi-schema.json index 9302e7db01..664b31f035 100644 --- a/qapi-schema.json +++ b/qapi-schema.json @@ -3286,7 +3286,7 @@ '*rows' : 'int' } } ## -# @ChardevRingbuf: +# @ChardevMemory: # # Configuration info for memory chardevs # @@ -3294,7 +3294,7 @@ # # Since: 1.5 ## -{ 'type': 'ChardevRingbuf', 'data': { '*size' : 'int' } } +{ 'type': 'ChardevMemory', 'data': { '*size' : 'int' } } ## # @ChardevBackend: @@ -3321,7 +3321,7 @@ 'spicevmc' : 'ChardevSpiceChannel', 'spiceport' : 'ChardevSpicePort', 'vc' : 'ChardevVC', - 'memory' : 'ChardevRingbuf' } } + 'memory' : 'ChardevMemory' } } ## # @ChardevReturn: |