Now that I have looked at these, I have a couple of comments... Amit Vadhavana <av2082000@xxxxxxxxx> writes: > Corrected spelling mistakes in the documentation to improve readability. Normal form for a changelog is to use the imperative mode; some maintainers are insistent about that. So "Correct spelling ... " > Signed-off-by: Amit Vadhavana <av2082000@xxxxxxxxx> > --- > Documentation/arch/arm/stm32/stm32-dma-mdma-chaining.rst | 4 ++-- > Documentation/arch/arm64/cpu-hotplug.rst | 2 +- > Documentation/arch/powerpc/ultravisor.rst | 2 +- > Documentation/arch/riscv/vector.rst | 2 +- > Documentation/arch/sparc/oradax/oracle-dax.rst | 2 +- > Documentation/arch/x86/mds.rst | 2 +- > Documentation/arch/x86/x86_64/fsgs.rst | 4 ++-- > Documentation/process/backporting.rst | 6 +++--- > 8 files changed, 12 insertions(+), 12 deletions(-) [...] > diff --git a/Documentation/arch/riscv/vector.rst b/Documentation/arch/riscv/vector.rst > index 75dd88a62e1d..e4a28def318a 100644 > --- a/Documentation/arch/riscv/vector.rst > +++ b/Documentation/arch/riscv/vector.rst > @@ -15,7 +15,7 @@ status for the use of Vector in userspace. The intended usage guideline for > these interfaces is to give init systems a way to modify the availability of V > for processes running under its domain. Calling these interfaces is not > recommended in libraries routines because libraries should not override policies > -configured from the parant process. Also, users must noted that these interfaces > +configured from the parent process. Also, users must noted that these interfaces As long as you are fixing this line, s/noted/note/ > are not portable to non-Linux, nor non-RISC-V environments, so it is discourage > to use in a portable code. To get the availability of V in an ELF program, > please read :c:macro:`COMPAT_HWCAP_ISA_V` bit of :c:macro:`ELF_HWCAP` in the > diff --git a/Documentation/arch/sparc/oradax/oracle-dax.rst b/Documentation/arch/sparc/oradax/oracle-dax.rst > index d1e14d572918..54ccb35ed51d 100644 > --- a/Documentation/arch/sparc/oradax/oracle-dax.rst > +++ b/Documentation/arch/sparc/oradax/oracle-dax.rst > @@ -197,7 +197,7 @@ Memory Constraints > ================== > > The DAX hardware operates only on physical addresses. Therefore, it is > -not aware of virtual memory mappings and the discontiguities that may > +not aware of virtual memory mappings and the discontinuities that may Whether "discontiguities" is recognized by a spelling checker or not, I expect that is the word that was intended by the author of this document. I would not change it. > exist in the physical memory that a virtual buffer maps to. There is > no I/O TLB or any scatter/gather mechanism. All buffers, whether input > or output, must reside in a physically contiguous region of memory. > diff --git a/Documentation/arch/x86/mds.rst b/Documentation/arch/x86/mds.rst > index c58c72362911..5a2e6c0ef04a 100644 > --- a/Documentation/arch/x86/mds.rst > +++ b/Documentation/arch/x86/mds.rst > @@ -162,7 +162,7 @@ Mitigation points > 3. It would take a large number of these precisely-timed NMIs to mount > an actual attack. There's presumably not enough bandwidth. > 4. The NMI in question occurs after a VERW, i.e. when user state is > - restored and most interesting data is already scrubbed. Whats left > + restored and most interesting data is already scrubbed. What's left > is only the data that NMI touches, and that may or may not be of > any interest. > > diff --git a/Documentation/arch/x86/x86_64/fsgs.rst b/Documentation/arch/x86/x86_64/fsgs.rst > index 50960e09e1f6..d07e445dac5c 100644 > --- a/Documentation/arch/x86/x86_64/fsgs.rst > +++ b/Documentation/arch/x86/x86_64/fsgs.rst > @@ -125,7 +125,7 @@ FSGSBASE instructions enablement > FSGSBASE instructions compiler support > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > -GCC version 4.6.4 and newer provide instrinsics for the FSGSBASE > +GCC version 4.6.4 and newer provide intrinsics for the FSGSBASE > instructions. Clang 5 supports them as well. Note that current kernels require rather newer versions of both compilers than this, so this information does not need to be here at all. If you do not want to edit at that level, though, the change is an improvement. Thanks, jon
