contrib/: fix some comment spelling errors

I found that there are many spelling errors in the comments of qemu,
so I used the spellcheck tool to check the spelling errors
and finally found some spelling errors in the contrib folder.

Signed-off-by: zhaolichang <zhaolichang@huawei.com>
Reviewed-by: Alex Bennee <alex.bennee@linaro.org>
Message-Id: <20200917075029.313-11-zhaolichang@huawei.com>
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
This commit is contained in:
zhaolichang 2020-09-17 15:50:29 +08:00 committed by Laurent Vivier
parent 2400e50c15
commit 639b090df5
4 changed files with 7 additions and 7 deletions

View File

@ -22,7 +22,7 @@
# in the gitdm sample-config directory. # in the gitdm sample-config directory.
# #
# This file contains associations parameters regarding filetypes # This file contains associations parameters regarding filetypes
# (documentation, develompent, multimedia, images...) # (documentation, development, multimedia, images...)
# #
# format: # format:
# filetype <type> <regex> [<comment>] # filetype <type> <regex> [<comment>]
@ -59,8 +59,8 @@ filetype code \.s$ # Assembly
filetype code \.S$ # Assembly filetype code \.S$ # Assembly
filetype code \.asm$ # Assembly filetype code \.asm$ # Assembly
filetype code \.awk$ # awk filetype code \.awk$ # awk
filetype code ^common$ # script fragements filetype code ^common$ # script fragments
filetype code ^common.*$ # script fragements filetype code ^common.*$ # script fragments
filetype code (qom|qmp)-\w+$ # python script fragments filetype code (qom|qmp)-\w+$ # python script fragments
# #

View File

@ -174,7 +174,7 @@ int ivshmem_client_notify_all_vects(const IvshmemClient *client,
const IvshmemClientPeer *peer); const IvshmemClientPeer *peer);
/** /**
* Broadcat a notification to all vectors of all peers * Broadcast a notification to all vectors of all peers
* *
* @client: The ivshmem client * @client: The ivshmem client
* *

View File

@ -684,7 +684,7 @@ vu_add_mem_reg(VuDev *dev, VhostUserMsg *vmsg) {
/* /*
* If we are in postcopy mode and we receive a u64 payload with a 0 value * If we are in postcopy mode and we receive a u64 payload with a 0 value
* we know all the postcopy client bases have been recieved, and we * we know all the postcopy client bases have been received, and we
* should start generating faults. * should start generating faults.
*/ */
if (track_ramblocks && if (track_ramblocks &&
@ -973,7 +973,7 @@ vu_set_mem_table_exec(VuDev *dev, VhostUserMsg *vmsg)
for (i = 0; i < dev->max_queues; i++) { for (i = 0; i < dev->max_queues; i++) {
if (dev->vq[i].vring.desc) { if (dev->vq[i].vring.desc) {
if (map_ring(dev, &dev->vq[i])) { if (map_ring(dev, &dev->vq[i])) {
vu_panic(dev, "remaping queue %d during setmemtable", i); vu_panic(dev, "remapping queue %d during setmemtable", i);
} }
} }
} }

View File

@ -424,7 +424,7 @@ typedef struct VuVirtqElement {
* @remove_watch: a remove_watch callback * @remove_watch: a remove_watch callback
* @iface: a VuDevIface structure with vhost-user device callbacks * @iface: a VuDevIface structure with vhost-user device callbacks
* *
* Intializes a VuDev vhost-user context. * Initializes a VuDev vhost-user context.
* *
* Returns: true on success, false on failure. * Returns: true on success, false on failure.
**/ **/