Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

docs: powerpc: Fix misspellings and grammar errors

Reported-by: Hulk Robot <hulkci@huawei.com>
Signed-off-by: He Ying <heying24@huawei.com>
Acked-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20210326100853.173586-1-heying24@huawei.com
Signed-off-by: Jonathan Corbet <corbet@lwn.net>

authored by

He Ying and committed by
Jonathan Corbet
f8b42777 abb9c078

+11 -11
+1 -1
Documentation/powerpc/booting.rst
··· 94 94 95 95 a) add your platform support as a _boolean_ option in 96 96 arch/powerpc/Kconfig, following the example of PPC_PSERIES, 97 - PPC_PMAC and PPC_MAPLE. The later is probably a good 97 + PPC_PMAC and PPC_MAPLE. The latter is probably a good 98 98 example of a board support to start from. 99 99 100 100 b) create your main platform file as
+1 -1
Documentation/powerpc/dawr-power9.rst
··· 4 4 5 5 On POWER9 the Data Address Watchpoint Register (DAWR) can cause a checkstop 6 6 if it points to cache inhibited (CI) memory. Currently Linux has no way to 7 - disinguish CI memory when configuring the DAWR, so (for now) the DAWR is 7 + distinguish CI memory when configuring the DAWR, so (for now) the DAWR is 8 8 disabled by this commit:: 9 9 10 10 commit 9654153158d3e0684a1bdb76dbababdb7111d5a0
+1 -1
Documentation/powerpc/eeh-pci-error-recovery.rst
··· 73 73 This value was chosen because it is the same value you would 74 74 get if the device was physically unplugged from the slot. 75 75 This includes access to PCI memory, I/O space, and PCI config 76 - space. Interrupts; however, will continued to be delivered. 76 + space. Interrupts; however, will continue to be delivered. 77 77 78 78 Detection and recovery are performed with the aid of ppc64 79 79 firmware. The programming interfaces in the Linux kernel
+1 -1
Documentation/powerpc/elfnote.rst
··· 8 8 Types and Descriptors 9 9 --------------------- 10 10 11 - The types to be used with the "PowerPC" namesapce are defined in [#f1]_. 11 + The types to be used with the "PowerPC" namespace are defined in [#f1]_. 12 12 13 13 1) PPC_ELFNOTE_CAPABILITIES 14 14
+1 -1
Documentation/powerpc/firmware-assisted-dump.rst
··· 207 207 user intervention. The dump data available through /proc/vmcore will be 208 208 in ELF format. Hence the existing kdump infrastructure (kdump scripts) 209 209 to save the dump works fine with minor modifications. KDump scripts on 210 - major Distro releases have already been modified to work seemlessly (no 210 + major Distro releases have already been modified to work seamlessly (no 211 211 user intervention in saving the dump) when FADump is used, instead of 212 212 KDump, as dump mechanism. 213 213
+1 -1
Documentation/powerpc/kaslr-booke32.rst
··· 38 38 39 39 kernstart_virt_addr 40 40 41 - To enable KASLR, set CONFIG_RANDOMIZE_BASE = y. If KASLR is enable and you 41 + To enable KASLR, set CONFIG_RANDOMIZE_BASE = y. If KASLR is enabled and you 42 42 want to disable it at runtime, add "nokaslr" to the kernel cmdline.
+1 -1
Documentation/powerpc/mpc52xx.rst
··· 34 34 Some remarks: 35 35 36 36 - The port is named mpc52xxx, and config options are PPC_MPC52xx. The MGT5100 37 - is not supported, and I'm not sure anyone is interesting in working on it 37 + is not supported, and I'm not sure anyone is interested in working on it 38 38 so. I didn't took 5xxx because there's apparently a lot of 5xxx that have 39 39 nothing to do with the MPC5200. I also included the 'MPC' for the same 40 40 reason.
+2 -2
Documentation/powerpc/papr_hcalls.rst
··· 40 40 have to be passed through a memory buffer, the data stored in that buffer should be 41 41 in Big-endian byte order. 42 42 43 - Once control is returns back to the guest after hypervisor has serviced the 43 + Once control returns back to the guest after hypervisor has serviced the 44 44 'HVCS' instruction the return value of the hcall is available in *r3* and any 45 45 out values are returned in registers *r4-r12*. Again like in case of in-arguments, 46 46 any out values stored in a memory buffer will be in Big-endian byte order. ··· 147 147 | Out: *numBytesRead* 148 148 | Return Value: *H_Success, H_Parameter, H_P2, H_P3, H_Hardware* 149 149 150 - Given a DRC Index of an NVDIMM, read N-bytes from the the metadata area 150 + Given a DRC Index of an NVDIMM, read N-bytes from the metadata area 151 151 associated with it, at a specified offset and copy it to provided buffer. 152 152 The metadata area stores configuration information such as label information, 153 153 bad-blocks etc. The metadata area is located out-of-band of NVDIMM storage
+2 -2
Documentation/powerpc/transactional_memory.rst
··· 189 189 ====================== ================================ 190 190 191 191 These can be checked by the user program's abort handler as TEXASR[0:7]. If 192 - bit 7 is set, it indicates that the error is consider persistent. For example 192 + bit 7 is set, it indicates that the error is considered persistent. For example 193 193 a TM_CAUSE_ALIGNMENT will be persistent while a TM_CAUSE_RESCHED will not. 194 194 195 195 GDB ··· 271 271 272 272 hrfid and mtmsrd have the same quirk. 273 273 274 - The Linux kernel uses this quirk in it's early exception handling. 274 + The Linux kernel uses this quirk in its early exception handling.