@@ -1313,7 +1313,7 @@ Removing "unreachable" stuff like events that can't be triggered
anymore, optional return or event data members that can't be sent
anymore, and return or event data member (enumeration) values that
can't be sent anymore makes no difference to clients, except for
-introspection. The latter can conceivably confuse clients, so tread
+introspection. The latter can conceivably confuse clients, so treat
carefully.
Incompatible changes include removing return and event data members.
@@ -99,7 +99,7 @@ successfully on various hosts. The following list shows some best practices:
* If your test cases uses the blkdebug feature, use relative path to pass
the config and image file paths in the command line as Windows absolute
path contains the delimiter ":" which will confuse the blkdebug parser.
-* Use double quotes in your extra QEMU commmand line in your test cases
+* Use double quotes in your extra QEMU command line in your test cases
instead of single quotes, as Windows does not drop single quotes when
passing the command line to QEMU.
* Windows opens a file in text mode by default, while a POSIX compliant
@@ -433,7 +433,7 @@ additional constraints on the set of vector lengths supported by SME.
SME User-mode Default Vector Length Property
--------------------------------------------
-For qemu-aarch64, the cpu propery ``sme-default-vector-length=N`` is
+For qemu-aarch64, the cpu property ``sme-default-vector-length=N`` is
defined to mirror the Linux kernel parameter file
``/proc/sys/abi/sme_default_vector_length``. The default length, ``N``,
is in units of bytes and must be between 16 and 8192.
@@ -41,7 +41,7 @@ can be accessed by following steps.
$ qemu-system-loongarch64 -machine virt -m 4G -cpu la464-loongarch-cpu \
-smp 1 -bios QEMU_EFI.fd -kernel vmlinuz.efi -initrd initrd.img \
- -append "root=/dev/ram rdinit=/sbin/init consol e=ttyS0,115200" \
+ -append "root=/dev/ram rdinit=/sbin/init console e=ttyS0,115200" \
--nographic
Note: The running speed may be a little slow, as the performance of our
@@ -232,7 +232,7 @@ e.g.:
``:ok:server::security.:``
- will pass 'securty.' xattr's in listxattr from the server
+ will pass 'security.' xattr's in listxattr from the server
and ignore following rules.
``:ok:all:::``
@@ -1970,7 +1970,7 @@ void memory_region_clear_dirty_bitmap(MemoryRegion *mr, hwaddr start,
* querying the same page multiple times, which is especially useful for
* display updates where the scanlines often are not page aligned.
*
- * The dirty bitmap region which gets copyed into the snapshot (and
+ * The dirty bitmap region which gets copied into the snapshot (and
* cleared afterwards) can be larger than requested. The boundaries
* are rounded up/down so complete bitmap longs (covering 64 pages on
* 64bit hosts) can be copied over into the bitmap snapshot. Which
@@ -586,7 +586,7 @@
#
# @size: size of the memory region in bytes
#
-# @x-use-canonical-path-for-ramblock-id: if true, the canoncial path is used
+# @x-use-canonical-path-for-ramblock-id: if true, the canonical path is used
# for ramblock-id. Disable this for 4.0
# machine types or older to allow
# migration with newer QEMU versions.
@@ -1051,7 +1051,7 @@ SRST
details on the external interface.
``-device isa-ipmi-kcs,bmc=id[,ioport=val][,irq=val]``
- Add a KCS IPMI interafce on the ISA bus. This also adds a
+ Add a KCS IPMI interface on the ISA bus. This also adds a
corresponding ACPI and SMBIOS entries, if appropriate.
``bmc=id``
@@ -1071,7 +1071,7 @@ SRST
is 0xe4 and the default interrupt is 5.
``-device pci-ipmi-kcs,bmc=id``
- Add a KCS IPMI interafce on the PCI bus.
+ Add a KCS IPMI interface on the PCI bus.
``bmc=id``
The BMC to connect to, one of ipmi-bmc-sim or ipmi-bmc-extern above.
@@ -5248,7 +5248,7 @@ SRST
read the colo-compare git log.
``-object cryptodev-backend-builtin,id=id[,queues=queues]``
- Creates a cryptodev backend which executes crypto opreation from
+ Creates a cryptodev backend which executes crypto operation from
the QEMU cipher APIS. The id parameter is a unique ID that will
be used to reference this cryptodev backend from the
``virtio-crypto`` device. The queues parameter is optional,
@@ -5516,7 +5516,7 @@ SRST
file=/etc/qemu/vnc.allow
Finally the ``/etc/qemu/vnc.allow`` file would contain the list
- of x509 distingished names that are permitted access
+ of x509 distinguished names that are permitted access
::
@@ -392,7 +392,7 @@
##
# @guest-file-flush:
#
-# Write file changes bufferred in userspace to disk/kernel buffers
+# Write file changes buffered in userspace to disk/kernel buffers
#
# @handle: filehandle returned by guest-file-open
#
@@ -727,7 +727,7 @@ bool qtest_has_device(const char *device);
* qtest_qmp_device_add_qdict:
* @qts: QTestState instance to operate on
* @drv: Name of the device that should be added
- * @arguments: QDict with properties for the device to intialize
+ * @arguments: QDict with properties for the device to initialize
*
* Generic hot-plugging test via the device_add QMP command with properties
* supplied in form of QDict. Use NULL for empty properties list.
Most of them were found and fixed using codespell. Signed-off-by: Stefan Weil <sw@weilnetz.de> --- My focus was fixing typos which are relevant for the generated documentation. codespell finds many more typos in source code, and adding it to the continuous integration checks looks more and more like a good idea. Stefan docs/devel/qapi-code-gen.rst | 2 +- docs/devel/testing.rst | 2 +- docs/system/arm/cpu-features.rst | 2 +- docs/system/loongarch/loongson3.rst | 2 +- docs/tools/virtiofsd.rst | 2 +- include/exec/memory.h | 2 +- qapi/qom.json | 2 +- qemu-options.hx | 8 ++++---- qga/qapi-schema.json | 2 +- tests/qtest/libqtest.h | 2 +- 10 files changed, 13 insertions(+), 13 deletions(-)