Skip to contentSkip to conversation

docs: fix typo in printk-formats documentation

PATCH In review Ravindra Kumar Bundela 2 participants 6 messages Jun 1

lore
Share & tools
lore
#0 lore raw

PATCH 1/3 docs: fix typo in printk-formats documentation

---
 docs/misc/printk-formats.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
docs/misc/printk-formats.txt +1 -1
index ce32829dae..2cad98703b 100644
@@ -23,7 +23,7 @@ Bitmaps (e.g. cpumask/nodemask):
 
 Symbol/Function pointers:
 
-       %ps     Symbol name with condition offset and size (iff offset != 0)
+       %ps     Symbol name with conditional offset and size (iff offset != 0)
                  e.g.  printk
                        default_idle+0x78/0x7d
 
Signature · 1 line
2.51.0.windows.2
#1 lore raw

PATCH 2/3 docs: fix spelling of 'receive' in xen-command-line

---
 docs/misc/xen-command-line.pandoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
docs/misc/xen-command-line.pandoc +1 -1
index 8c89b7852c..ef3c737189 100644
@@ -191,7 +191,7 @@ The functionality that this option controls is only available when Xen has been
 compiled with the build setting for Argo enabled in the build configuration.
 
 Argo is a interdomain communication mechanism, where Xen acts as the central
-point of authority.  Guests may register memory rings to recieve messages,
+point of authority.  Guests may register memory rings to receive messages,
 query the status of other domains, and send messages by hypercall, all subject
 to appropriate auditing by Xen.  Argo is disabled by default.
 
Signature · 1 line
2.51.0.windows.2
Acked-by on v1 2/3
#2 lore raw

Re: [PATCH 2/3] docs: fix spelling of 'receive' in xen-command-line

Quoted 10 lines · Ravindra Kumar Bundela
---
 docs/misc/xen-command-line.pandoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
docs/misc/xen-command-line.pandoc +0 -0
index 8c89b7852c..ef3c737189 100644

docs/misc/xen-command-line.pandoc The functionality that this option controls is only available when Xen has been · line 197

Quoted 8 lines
docs/misc/xen-command-line.pandoc +1 -1
@@ -191,7 +191,7 @@ The functionality that this option controls is only available when Xen has been
 compiled with the build setting for Argo enabled in the build configuration.
 
 Argo is a interdomain communication mechanism, where Xen acts as the central
-point of authority.  Guests may register memory rings to recieve messages,
+point of authority.  Guests may register memory rings to receive messages,
 query the status of other domains, and send messages by hypercall, all subject
 to appropriate auditing by Xen.  Argo is disabled by default.
 

~Michal

#3 lore raw

PATCH 3/3 docs: fix spelling of 'receiver' and 'receiving' in libxc-migration-stream

In reply to Ravindra Kumar Bundela
---
 docs/specs/libxc-migration-stream.pandoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
docs/specs/libxc-migration-stream.pandoc +2 -2
index 8aeab3b11b..1319ce1f1e 100644
@@ -753,7 +753,7 @@ A v3 stream is compatible with a v2 stream, but mandates the presense of a
 STATIC_DATA_END record ahead of any memory/register content.  This is to ease
 the introduction of new static configuration records over time.
 
-A v3-compatible reciever interpreting a v2 stream should infer the position of
+A v3-compatible receiver interpreting a v2 stream should infer the position of
 STATIC_DATA_END based on finding the first X86_PV_P2M_FRAMES record (for PV
 guests), or PAGE_DATA record (for HVM guests) and behave as if STATIC_DATA_END
 had been sent.
@@ -807,7 +807,7 @@ never change size or location.
 Errata
 ======
 
-1. For compatibility with older code, the receving side of a stream should
+1. For compatibility with older code, the receiving side of a stream should
    tolerate and ignore variable sized records with zero content.  Xen releases
    between 4.6 and 4.8 could end up generating valid HVM_PARAMS or
    X86_PV_VCPU_{EXTENDED,XSAVE,MSRS} records with zero-length content.
Signature · 1 line
2.51.0.windows.2
Acked-by on v1 3/3
#4 lore raw

Re: [PATCH 3/3] docs: fix spelling of 'receiver' and 'receiving' in libxc-migration-stream

Quoted 19 lines · Ravindra Kumar Bundela
---
 docs/specs/libxc-migration-stream.pandoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
docs/specs/libxc-migration-stream.pandoc +1 -1
index 8aeab3b11b..1319ce1f1e 100644
@@ -753,7 +753,7 @@ A v3 stream is compatible with a v2 stream, but mandates the presense of a
 STATIC_DATA_END record ahead of any memory/register content.  This is to ease
 the introduction of new static configuration records over time.
 
-A v3-compatible reciever interpreting a v2 stream should infer the position of
+A v3-compatible receiver interpreting a v2 stream should infer the position of
 STATIC_DATA_END based on finding the first X86_PV_P2M_FRAMES record (for PV
 guests), or PAGE_DATA record (for HVM guests) and behave as if STATIC_DATA_END
 had been sent.

docs/specs/libxc-migration-stream.pandoc never change size or location. · line 813

Quoted 8 lines
docs/specs/libxc-migration-stream.pandoc +1 -1
@@ -807,7 +807,7 @@ never change size or location.
 Errata
 ======
 
-1. For compatibility with older code, the receving side of a stream should
+1. For compatibility with older code, the receiving side of a stream should
    tolerate and ignore variable sized records with zero content.  Xen releases
    between 4.6 and 4.8 could end up generating valid HVM_PARAMS or
    X86_PV_VCPU_{EXTENDED,XSAVE,MSRS} records with zero-length content.

~Michal

Acked-by on v1 1/3
#5 lore raw
In reply to Ravindra Kumar Bundela

Hello,

Thanks for your submission.
When sending patches, please CC relevant maintainers by using ./scripts/add_maintainers.pl (automatically adds them into the patch) or get_maintainers.pl.

Quoted 10 lines · Ravindra Kumar Bundela
---
 docs/misc/printk-formats.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
docs/misc/printk-formats.txt +0 -0
index ce32829dae..2cad98703b 100644

docs/misc/printk-formats.txt Bitmaps (e.g. cpumask/nodemask): · line 29

Quoted 8 lines
docs/misc/printk-formats.txt +1 -1
@@ -23,7 +23,7 @@ Bitmaps (e.g. cpumask/nodemask):
 
 Symbol/Function pointers:
 
-       %ps     Symbol name with condition offset and size (iff offset != 0)
+       %ps     Symbol name with conditional offset and size (iff offset != 0)
                  e.g.  printk
                        default_idle+0x78/0x7d
 

~Michal