From: Randy Dunlap <rdunlap@infradead.org> To: linux-kernel@vger.kernel.org Cc: Randy Dunlap <rdunlap@infradead.org>, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>, linux-arm-kernel@lists.infradead.org, Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org Subject: [PATCH 01/35] Documentation: arm64: correct spelling Date: Thu, 26 Jan 2023 22:39:32 -0800 [thread overview] Message-ID: <20230127064005.1558-3-rdunlap@infradead.org> (raw) In-Reply-To: <20230127064005.1558-1-rdunlap@infradead.org> Correct spelling problems for Documentation/arm64/ as reported by codespell. Signed-off-by: Randy Dunlap <rdunlap@infradead.org> Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Will Deacon <will@kernel.org> Cc: linux-arm-kernel@lists.infradead.org Cc: Jonathan Corbet <corbet@lwn.net> Cc: linux-doc@vger.kernel.org --- Documentation/arm64/booting.rst | 2 +- Documentation/arm64/elf_hwcaps.rst | 2 +- Documentation/arm64/sve.rst | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff -- a/Documentation/arm64/booting.rst b/Documentation/arm64/booting.rst --- a/Documentation/arm64/booting.rst +++ b/Documentation/arm64/booting.rst @@ -223,7 +223,7 @@ Before jumping into the kernel, the foll For systems with a GICv3 interrupt controller to be used in v3 mode: - If EL3 is present: - - ICC_SRE_EL3.Enable (bit 3) must be initialiased to 0b1. + - ICC_SRE_EL3.Enable (bit 3) must be initialised to 0b1. - ICC_SRE_EL3.SRE (bit 0) must be initialised to 0b1. - ICC_CTLR_EL3.PMHE (bit 6) must be set to the same value across all CPUs the kernel is executing on, and must stay constant diff -- a/Documentation/arm64/elf_hwcaps.rst b/Documentation/arm64/elf_hwcaps.rst --- a/Documentation/arm64/elf_hwcaps.rst +++ b/Documentation/arm64/elf_hwcaps.rst @@ -14,7 +14,7 @@ Some hardware or software features are o implementations, and/or with certain kernel configurations, but have no architected discovery mechanism available to userspace code at EL0. The kernel exposes the presence of these features to userspace through a set -of flags called hwcaps, exposed in the auxilliary vector. +of flags called hwcaps, exposed in the auxiliary vector. Userspace software can test for features by acquiring the AT_HWCAP or AT_HWCAP2 entry of the auxiliary vector, and testing whether the relevant diff -- a/Documentation/arm64/sve.rst b/Documentation/arm64/sve.rst --- a/Documentation/arm64/sve.rst +++ b/Documentation/arm64/sve.rst @@ -175,7 +175,7 @@ the SVE instruction set architecture. When returning from a signal handler: * If there is no sve_context record in the signal frame, or if the record is - present but contains no register data as desribed in the previous section, + present but contains no register data as described in the previous section, then the SVE registers/bits become non-live and take unspecified values. * If sve_context is present in the signal frame and contains full register @@ -223,7 +223,7 @@ prctl(PR_SVE_SET_VL, unsigned long arg) Defer the requested vector length change until the next execve() performed by this thread. - The effect is equivalent to implicit exceution of the following + The effect is equivalent to implicit execution of the following call immediately after the next execve() (if any) by the thread: prctl(PR_SVE_SET_VL, arg & ~PR_SVE_SET_VL_ONEXEC)
WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <rdunlap@infradead.org> To: linux-kernel@vger.kernel.org Cc: Randy Dunlap <rdunlap@infradead.org>, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>, linux-arm-kernel@lists.infradead.org, Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org Subject: [PATCH 01/35] Documentation: arm64: correct spelling Date: Thu, 26 Jan 2023 22:39:32 -0800 [thread overview] Message-ID: <20230127064005.1558-3-rdunlap@infradead.org> (raw) In-Reply-To: <20230127064005.1558-1-rdunlap@infradead.org> Correct spelling problems for Documentation/arm64/ as reported by codespell. Signed-off-by: Randy Dunlap <rdunlap@infradead.org> Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Will Deacon <will@kernel.org> Cc: linux-arm-kernel@lists.infradead.org Cc: Jonathan Corbet <corbet@lwn.net> Cc: linux-doc@vger.kernel.org --- Documentation/arm64/booting.rst | 2 +- Documentation/arm64/elf_hwcaps.rst | 2 +- Documentation/arm64/sve.rst | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff -- a/Documentation/arm64/booting.rst b/Documentation/arm64/booting.rst --- a/Documentation/arm64/booting.rst +++ b/Documentation/arm64/booting.rst @@ -223,7 +223,7 @@ Before jumping into the kernel, the foll For systems with a GICv3 interrupt controller to be used in v3 mode: - If EL3 is present: - - ICC_SRE_EL3.Enable (bit 3) must be initialiased to 0b1. + - ICC_SRE_EL3.Enable (bit 3) must be initialised to 0b1. - ICC_SRE_EL3.SRE (bit 0) must be initialised to 0b1. - ICC_CTLR_EL3.PMHE (bit 6) must be set to the same value across all CPUs the kernel is executing on, and must stay constant diff -- a/Documentation/arm64/elf_hwcaps.rst b/Documentation/arm64/elf_hwcaps.rst --- a/Documentation/arm64/elf_hwcaps.rst +++ b/Documentation/arm64/elf_hwcaps.rst @@ -14,7 +14,7 @@ Some hardware or software features are o implementations, and/or with certain kernel configurations, but have no architected discovery mechanism available to userspace code at EL0. The kernel exposes the presence of these features to userspace through a set -of flags called hwcaps, exposed in the auxilliary vector. +of flags called hwcaps, exposed in the auxiliary vector. Userspace software can test for features by acquiring the AT_HWCAP or AT_HWCAP2 entry of the auxiliary vector, and testing whether the relevant diff -- a/Documentation/arm64/sve.rst b/Documentation/arm64/sve.rst --- a/Documentation/arm64/sve.rst +++ b/Documentation/arm64/sve.rst @@ -175,7 +175,7 @@ the SVE instruction set architecture. When returning from a signal handler: * If there is no sve_context record in the signal frame, or if the record is - present but contains no register data as desribed in the previous section, + present but contains no register data as described in the previous section, then the SVE registers/bits become non-live and take unspecified values. * If sve_context is present in the signal frame and contains full register @@ -223,7 +223,7 @@ prctl(PR_SVE_SET_VL, unsigned long arg) Defer the requested vector length change until the next execve() performed by this thread. - The effect is equivalent to implicit exceution of the following + The effect is equivalent to implicit execution of the following call immediately after the next execve() (if any) by the thread: prctl(PR_SVE_SET_VL, arg & ~PR_SVE_SET_VL_ONEXEC) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-27 6:40 UTC|newest] Thread overview: 108+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-27 6:39 [PATCH 00/35] Documentation: correct lots of spelling errors (series 1) Randy Dunlap 2023-01-27 6:39 ` Randy Dunlap 2023-01-27 6:39 ` Randy Dunlap 2023-01-27 6:39 ` Randy Dunlap 2023-01-27 6:39 ` [PATCH 02/35] Documentation: arm: correct spelling Randy Dunlap 2023-01-27 6:39 ` Randy Dunlap 2023-01-27 6:55 ` Mukesh Ojha 2023-01-27 6:55 ` Mukesh Ojha 2023-01-27 6:39 ` Randy Dunlap [this message] 2023-01-27 6:39 ` [PATCH 01/35] Documentation: arm64: " Randy Dunlap 2023-01-27 7:02 ` Mukesh Ojha 2023-01-27 7:02 ` Mukesh Ojha 2023-01-27 6:39 ` [PATCH 03/35] Documentation: block: " Randy Dunlap 2023-01-27 8:31 ` Bagas Sanjaya 2023-01-27 22:58 ` Randy Dunlap 2023-01-27 8:36 ` Mukesh Ojha 2023-01-27 6:39 ` [PATCH 04/35] Documentation: bpf: " Randy Dunlap 2023-01-27 8:29 ` Bagas Sanjaya 2023-01-28 19:38 ` Alexei Starovoitov 2023-01-30 14:24 ` David Vernet 2023-01-30 14:26 ` David Vernet 2023-01-27 6:39 ` [PATCH 05/35] Documentation: core-api: " Randy Dunlap 2023-01-27 15:25 ` Mukesh Ojha 2023-01-27 6:39 ` [PATCH 06/35] Documentation: fault-injection: " Randy Dunlap 2023-01-27 6:39 ` [PATCH 07/35] Documentation: fb: " Randy Dunlap 2023-01-27 6:39 ` Randy Dunlap 2023-01-27 6:39 ` [PATCH 08/35] Documentation: features: " Randy Dunlap 2023-01-27 6:39 ` [PATCH 09/35] Documentation: firmware-guide/acpi: " Randy Dunlap 2023-01-30 15:52 ` Rafael J. Wysocki 2023-01-27 6:39 ` [PATCH 10/35] Documentation: hid: " Randy Dunlap 2023-01-27 16:20 ` srinivas pandruvada 2023-02-06 14:01 ` (subset) " Benjamin Tissoires 2023-01-27 6:39 ` [PATCH 11/35] Documentation: i2c: " Randy Dunlap 2023-01-27 7:14 ` Wolfram Sang 2023-01-27 8:26 ` Bagas Sanjaya 2023-01-27 22:34 ` Randy Dunlap 2023-01-27 6:39 ` [PATCH 12/35] Documentation: input: " Randy Dunlap 2023-01-27 6:39 ` [PATCH 13/35] Documentation: isdn: " Randy Dunlap 2023-01-28 6:06 ` Jakub Kicinski 2023-01-27 6:39 ` [PATCH 14/35] Documentation: leds: " Randy Dunlap 2023-01-27 9:30 ` Lee Jones 2023-01-27 6:39 ` [PATCH 15/35] Documentation: litmus-tests: " Randy Dunlap 2023-01-27 6:39 ` [PATCH 16/35] Documentation: livepatch: " Randy Dunlap 2023-01-27 10:52 ` Petr Mladek 2023-01-27 6:39 ` [PATCH 17/35] Documentation: locking: " Randy Dunlap 2023-01-27 6:39 ` [PATCH 18/35] Documentation: mm: " Randy Dunlap 2023-01-27 6:44 ` HORIGUCHI NAOYA(堀口 直也) 2023-01-27 8:27 ` Bagas Sanjaya 2023-01-30 10:07 ` Mike Rapoport 2023-01-27 6:39 ` [PATCH 19/35] Documentation: openrisc: " Randy Dunlap 2023-01-27 6:39 ` Randy Dunlap 2023-01-27 6:39 ` [PATCH 20/35] Documentation: PCI: " Randy Dunlap 2023-01-27 15:55 ` Bjorn Helgaas 2023-01-27 6:39 ` [PATCH 22/35] Documentation: power: " Randy Dunlap 2023-01-27 6:39 ` [PATCH 21/35] Documentation: powerpc: " Randy Dunlap 2023-01-27 6:39 ` Randy Dunlap 2023-01-27 6:39 ` [PATCH 23/35] Documentation: s390: " Randy Dunlap 2023-01-27 11:43 ` Heiko Carstens 2023-01-27 6:39 ` [PATCH 24/35] Documentation: scheduler: " Randy Dunlap 2023-01-27 15:33 ` Mukesh Ojha 2023-01-27 6:39 ` [PATCH 25/35] Documentation: security: " Randy Dunlap 2023-01-27 6:39 ` [PATCH 26/35] Documentation: sound: " Randy Dunlap 2023-01-27 6:39 ` Randy Dunlap 2023-01-29 8:24 ` Takashi Iwai 2023-01-29 8:24 ` Takashi Iwai 2023-01-27 6:39 ` [PATCH 27/35] Documentation: spi: " Randy Dunlap 2023-01-27 6:39 ` [PATCH 28/35] Documentation: target: " Randy Dunlap 2023-02-08 23:13 ` Martin K. Petersen 2023-01-27 6:39 ` [PATCH 29/35] Documentation: timers: " Randy Dunlap 2023-01-27 6:40 ` [PATCH 30/35] Documentation: tools/rtla: " Randy Dunlap 2023-01-27 8:52 ` Daniel Bristot de Oliveira 2023-01-27 19:53 ` Steven Rostedt 2023-01-27 6:40 ` [PATCH 31/35] Documentation: trace: " Randy Dunlap 2023-01-27 6:40 ` Randy Dunlap 2023-01-27 7:05 ` Mukesh Ojha 2023-01-27 7:05 ` Mukesh Ojha 2023-01-27 8:54 ` Daniel Bristot de Oliveira 2023-01-27 8:54 ` Daniel Bristot de Oliveira 2023-01-27 23:01 ` Randy Dunlap 2023-01-27 23:01 ` Randy Dunlap 2023-01-27 19:54 ` Steven Rostedt 2023-01-27 19:54 ` Steven Rostedt 2023-01-31 18:20 ` Suzuki K Poulose 2023-01-31 18:20 ` Suzuki K Poulose 2023-01-27 6:40 ` [PATCH 32/35] Documentation: usb: " Randy Dunlap 2023-01-27 6:40 ` [PATCH 33/35] Documentation: w1: " Randy Dunlap 2023-01-27 6:40 ` [PATCH 34/35] Documentation: x86: " Randy Dunlap 2023-01-27 6:40 ` [PATCH 35/35] Documentation: xtensa: " Randy Dunlap 2023-01-27 17:45 ` Max Filippov 2023-01-27 6:59 ` [PATCH 15/35] Documentation: litmus-tests: " David Howells 2023-01-27 14:59 ` Paul E. McKenney 2023-01-27 6:59 ` [PATCH 25/35] Documentation: security: " David Howells 2023-01-28 10:48 ` (subset) [PATCH 00/35] Documentation: correct lots of spelling errors (series 1) Mark Brown 2023-01-28 10:48 ` Mark Brown 2023-01-28 10:48 ` Mark Brown 2023-01-28 10:48 ` Mark Brown 2023-01-28 20:30 ` patchwork-bot+netdevbpf 2023-01-28 20:30 ` patchwork-bot+netdevbpf 2023-01-28 20:30 ` patchwork-bot+netdevbpf 2023-01-28 20:30 ` patchwork-bot+netdevbpf 2023-01-31 16:28 ` (subset) " Catalin Marinas 2023-01-31 16:28 ` Catalin Marinas 2023-01-31 16:28 ` Catalin Marinas 2023-01-31 16:28 ` Catalin Marinas 2023-02-14 16:57 ` Martin K. Petersen 2023-02-14 16:57 ` Martin K. Petersen 2023-02-14 16:57 ` Martin K. Petersen 2023-02-14 16:57 ` Martin K. Petersen
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20230127064005.1558-3-rdunlap@infradead.org \ --to=rdunlap@infradead.org \ --cc=catalin.marinas@arm.com \ --cc=corbet@lwn.net \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-doc@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=will@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.