docs/about/deprecated.rst | 2 +- docs/devel/qom.rst | 2 +- docs/system/devices/nvme.rst | 2 +- hw/core/loader.c | 4 ++-- include/exec/memory.h | 2 +- ui/vnc-enc-tight.c | 2 +- 6 files changed, 7 insertions(+), 7 deletions(-)
Signed-off-by: Stefan Weil <sw@weilnetz.de>
---
This patch was triggered by a spelling check for the generated
QEMU documentation using codespell. It does not try to fix all
typos which still exist in the QEMU code, but has a focus on
those required to fix the documentation. Nevertheless some code
comments with the same typos were fixed, too.
I think the patch is trivial, so maybe it can still be included
in the upcoming release, but that's not strictly necessary.
Stefan
docs/about/deprecated.rst | 2 +-
docs/devel/qom.rst | 2 +-
docs/system/devices/nvme.rst | 2 +-
hw/core/loader.c | 4 ++--
include/exec/memory.h | 2 +-
ui/vnc-enc-tight.c | 2 +-
6 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst
index 1c35f55666..92a2bafd2b 100644
--- a/docs/about/deprecated.rst
+++ b/docs/about/deprecated.rst
@@ -369,7 +369,7 @@ mapping permissions et al by using its 'mapped' security model option.
Nowadays it would make sense to reimplement the ``proxy`` backend by using
QEMU's ``vhost`` feature, which would eliminate the high latency costs under
which the 9p ``proxy`` backend currently suffers. However as of to date nobody
-has indicated plans for such kind of reimplemention unfortunately.
+has indicated plans for such kind of reimplementation unfortunately.
Block device options
diff --git a/docs/devel/qom.rst b/docs/devel/qom.rst
index 0b506426d7..9918fac7f2 100644
--- a/docs/devel/qom.rst
+++ b/docs/devel/qom.rst
@@ -30,7 +30,7 @@ user configuration.
Creating a QOM class
====================
-A simple minimal device implementation may look something like bellow:
+A simple minimal device implementation may look something like below:
.. code-block:: c
:caption: Creating a minimal type
diff --git a/docs/system/devices/nvme.rst b/docs/system/devices/nvme.rst
index a8bb8d729c..2a3af268f7 100644
--- a/docs/system/devices/nvme.rst
+++ b/docs/system/devices/nvme.rst
@@ -232,7 +232,7 @@ parameters:
Set the number of Reclaim Groups.
``fdp.nruh`` (default: ``0``)
- Set the number of Reclaim Unit Handles. This is a mandatory paramater and
+ Set the number of Reclaim Unit Handles. This is a mandatory parameter and
must be non-zero.
``fdp.runs`` (default: ``96M``)
diff --git a/hw/core/loader.c b/hw/core/loader.c
index 8b7fd9e9e5..4dd5a71fb7 100644
--- a/hw/core/loader.c
+++ b/hw/core/loader.c
@@ -863,7 +863,7 @@ ssize_t load_image_gzipped(const char *filename, hwaddr addr, uint64_t max_sz)
/*
* The Linux header magic number for a EFI PE/COFF
- * image targetting an unspecified architecture.
+ * image targeting an unspecified architecture.
*/
#define EFI_PE_LINUX_MAGIC "\xcd\x23\x82\x81"
@@ -1492,7 +1492,7 @@ RomGap rom_find_largest_gap_between(hwaddr base, size_t size)
if (rom->mr || rom->fw_file) {
continue;
}
- /* ignore anything finishing bellow base */
+ /* ignore anything finishing below base */
if (rom->addr + rom->romsize <= base) {
continue;
}
diff --git a/include/exec/memory.h b/include/exec/memory.h
index 7f5c11a0cc..68284428f8 100644
--- a/include/exec/memory.h
+++ b/include/exec/memory.h
@@ -942,7 +942,7 @@ struct MemoryListener {
*
* @listener: The #MemoryListener.
* @last_stage: The last stage to synchronize the log during migration.
- * The caller should gurantee that the synchronization with true for
+ * The caller should guarantee that the synchronization with true for
* @last_stage is triggered for once after all VCPUs have been stopped.
*/
void (*log_sync_global)(MemoryListener *listener, bool last_stage);
diff --git a/ui/vnc-enc-tight.c b/ui/vnc-enc-tight.c
index 09200d71b8..ee853dcfcb 100644
--- a/ui/vnc-enc-tight.c
+++ b/ui/vnc-enc-tight.c
@@ -77,7 +77,7 @@ static int tight_send_framebuffer_update(VncState *vs, int x, int y,
#ifdef CONFIG_VNC_JPEG
static const struct {
- double jpeg_freq_min; /* Don't send JPEG if the freq is bellow */
+ double jpeg_freq_min; /* Don't send JPEG if the freq is below */
double jpeg_freq_threshold; /* Always send JPEG if the freq is above */
int jpeg_idx; /* Allow indexed JPEG */
int jpeg_full; /* Allow full color JPEG */
--
2.39.230.07.2023 21:03, Stefan Weil via wrote: > Signed-off-by: Stefan Weil <sw@weilnetz.de> > --- > > This patch was triggered by a spelling check for the generated > QEMU documentation using codespell. It does not try to fix all > typos which still exist in the QEMU code, but has a focus on > those required to fix the documentation. Nevertheless some code > comments with the same typos were fixed, too. > > I think the patch is trivial, so maybe it can still be included > in the upcoming release, but that's not strictly necessary. > > Stefan > > docs/about/deprecated.rst | 2 +- > docs/devel/qom.rst | 2 +- > docs/system/devices/nvme.rst | 2 +- > hw/core/loader.c | 4 ++-- > include/exec/memory.h | 2 +- > ui/vnc-enc-tight.c | 2 +- > 6 files changed, 7 insertions(+), 7 deletions(-) > > diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst > index 1c35f55666..92a2bafd2b 100644 > --- a/docs/about/deprecated.rst > +++ b/docs/about/deprecated.rst > @@ -369,7 +369,7 @@ mapping permissions et al by using its 'mapped' security model option. > Nowadays it would make sense to reimplement the ``proxy`` backend by using > QEMU's ``vhost`` feature, which would eliminate the high latency costs under > which the 9p ``proxy`` backend currently suffers. However as of to date nobody > -has indicated plans for such kind of reimplemention unfortunately. > +has indicated plans for such kind of reimplementation unfortunately. FWIW, all these changes has been included in my "tree-wide spelling" series. This particular change: https://lists.nongnu.org/archive/html/qemu-devel/2023-07/msg03011.html /mjt
On 30/7/23 20:03, Stefan Weil wrote: > Signed-off-by: Stefan Weil <sw@weilnetz.de> > --- > > This patch was triggered by a spelling check for the generated > QEMU documentation using codespell. It does not try to fix all > typos which still exist in the QEMU code, but has a focus on > those required to fix the documentation. Nevertheless some code > comments with the same typos were fixed, too. > > I think the patch is trivial, so maybe it can still be included > in the upcoming release, but that's not strictly necessary. > > Stefan > > docs/about/deprecated.rst | 2 +- > docs/devel/qom.rst | 2 +- > docs/system/devices/nvme.rst | 2 +- > hw/core/loader.c | 4 ++-- > include/exec/memory.h | 2 +- > ui/vnc-enc-tight.c | 2 +- > 6 files changed, 7 insertions(+), 7 deletions(-) Thanks, queued via misc-fixes.
On 30/7/23 20:03, Stefan Weil wrote: > Signed-off-by: Stefan Weil <sw@weilnetz.de> > --- > > This patch was triggered by a spelling check for the generated > QEMU documentation using codespell. It does not try to fix all > typos which still exist in the QEMU code, but has a focus on > those required to fix the documentation. Nevertheless some code > comments with the same typos were fixed, too. > > I think the patch is trivial, so maybe it can still be included > in the upcoming release, but that's not strictly necessary. > > Stefan > > docs/about/deprecated.rst | 2 +- > docs/devel/qom.rst | 2 +- > docs/system/devices/nvme.rst | 2 +- > hw/core/loader.c | 4 ++-- > include/exec/memory.h | 2 +- > ui/vnc-enc-tight.c | 2 +- > 6 files changed, 7 insertions(+), 7 deletions(-) Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
On Sun, 30 Jul 2023 at 19:55, Stefan Weil via <qemu-devel@nongnu.org> wrote: > > Signed-off-by: Stefan Weil <sw@weilnetz.de> > --- Reviewed-by: Peter Maydell <peter.maydell@linaro.org> thanks -- PMM
© 2016 - 2024 Red Hat, Inc.