From: Mukesh Ojha <quic_mojha@quicinc.com>
To: Randy Dunlap <rdunlap@infradead.org>, <linux-kernel@vger.kernel.org>
Cc: Russell King <linux@armlinux.org.uk>,
<linux-arm-kernel@lists.infradead.org>,
Jonathan Corbet <corbet@lwn.net>, <linux-doc@vger.kernel.org>
Subject: Re: [PATCH 02/35] Documentation: arm: correct spelling
Date: Fri, 27 Jan 2023 12:25:32 +0530 [thread overview]
Message-ID: <3d99cf40-b5e2-21da-cc37-cd2e17ce10ad@quicinc.com> (raw)
In-Reply-To: <20230127064005.1558-2-rdunlap@infradead.org>
Hi,
Thanks for the patch.
On 1/27/2023 12:09 PM, Randy Dunlap wrote:
> Correct spelling problems for Documentation/arm/ as reported
> by codespell.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Russell King <linux@armlinux.org.uk>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> ---
> Documentation/arm/arm.rst | 2 +-
> Documentation/arm/ixp4xx.rst | 4 ++--
> Documentation/arm/keystone/knav-qmss.rst | 2 +-
> Documentation/arm/stm32/stm32-dma-mdma-chaining.rst | 6 +++---
> Documentation/arm/sunxi/clocks.rst | 2 +-
> Documentation/arm/swp_emulation.rst | 2 +-
> Documentation/arm/tcm.rst | 2 +-
> Documentation/arm/vlocks.rst | 2 +-
> 8 files changed, 11 insertions(+), 11 deletions(-)
>
> diff -- a/Documentation/arm/ixp4xx.rst b/Documentation/arm/ixp4xx.rst
> --- a/Documentation/arm/ixp4xx.rst
> +++ b/Documentation/arm/ixp4xx.rst
> @@ -78,9 +78,9 @@ IXP4xx provides two methods of accessing
> 1) A direct mapped window from 0x48000000 to 0x4bffffff (64MB).
> To access PCI via this space, we simply ioremap() the BAR
> into the kernel and we can use the standard read[bwl]/write[bwl]
> - macros. This is the preffered method due to speed but it
> + macros. This is the preferred method due to speed but it
> limits the system to just 64MB of PCI memory. This can be
> - problamatic if using video cards and other memory-heavy devices.
> + problematic if using video cards and other memory-heavy devices.
>
> 2) If > 64MB of memory space is required, the IXP4xx can be
> configured to use indirect registers to access PCI This allows
> diff -- a/Documentation/arm/swp_emulation.rst b/Documentation/arm/swp_emulation.rst
> --- a/Documentation/arm/swp_emulation.rst
> +++ b/Documentation/arm/swp_emulation.rst
> @@ -1,7 +1,7 @@
> Software emulation of deprecated SWP instruction (CONFIG_SWP_EMULATE)
> ---------------------------------------------------------------------
>
> -ARMv6 architecture deprecates use of the SWP/SWPB instructions, and recommeds
> +ARMv6 architecture deprecates use of the SWP/SWPB instructions, and recommends
> moving to the load-locked/store-conditional instructions LDREX and STREX.
>
> ARMv7 multiprocessing extensions introduce the ability to disable these
> diff -- a/Documentation/arm/tcm.rst b/Documentation/arm/tcm.rst
> --- a/Documentation/arm/tcm.rst
> +++ b/Documentation/arm/tcm.rst
> @@ -71,7 +71,7 @@ in <asm/tcm.h>. Using this interface it
>
> - Have the remaining TCM RAM added to a special
> allocation pool with gen_pool_create() and gen_pool_add()
> - and provice tcm_alloc() and tcm_free() for this
> + and provide tcm_alloc() and tcm_free() for this
> memory. Such a heap is great for things like saving
> device state when shutting off device power domains.
>
> diff -- a/Documentation/arm/stm32/stm32-dma-mdma-chaining.rst b/Documentation/arm/stm32/stm32-dma-mdma-chaining.rst
> --- a/Documentation/arm/stm32/stm32-dma-mdma-chaining.rst
> +++ b/Documentation/arm/stm32/stm32-dma-mdma-chaining.rst
> @@ -359,7 +359,7 @@ Driver updates for STM32 DMA-MDMA chaini
> descriptor you want a callback to be called at the end of the transfer
> (dmaengine_prep_slave_sg()) or the period (dmaengine_prep_dma_cyclic()).
> Depending on the direction, set the callback on the descriptor that finishes
> - the overal transfer:
> + the overall transfer:
>
> * DMA_DEV_TO_MEM: set the callback on the "MDMA" descriptor
> * DMA_MEM_TO_DEV: set the callback on the "DMA" descriptor
> @@ -371,7 +371,7 @@ Driver updates for STM32 DMA-MDMA chaini
> As STM32 MDMA channel transfer is triggered by STM32 DMA, you must issue
> STM32 MDMA channel before STM32 DMA channel.
>
> - If any, your callback will be called to warn you about the end of the overal
> + If any, your callback will be called to warn you about the end of the overall
> transfer or the period completion.
>
> Don't forget to terminate both channels. STM32 DMA channel is configured in
> @@ -412,4 +412,4 @@ Resources
>
> :Authors:
>
> -- Amelie Delaunay <amelie.delaunay@foss.st.com>
> \ No newline at end of file
> +- Amelie Delaunay <amelie.delaunay@foss.st.com>
> diff -- a/Documentation/arm/arm.rst b/Documentation/arm/arm.rst
> --- a/Documentation/arm/arm.rst
> +++ b/Documentation/arm/arm.rst
> @@ -141,7 +141,7 @@ ST506 hard drives
> `*configure` harddrive set to 2). I've got an internal 20MB and a great
> big external 5.25" FH 64MB drive (who could ever want more :-) ).
>
> - I've just got 240K/s off it (a dd with bs=128k); thats about half of what
> + I've just got 240K/s off it (a dd with bs=128k); that's about half of what
> RiscOS gets; but it's a heck of a lot better than the 50K/s I was getting
> last week :-)
>
> diff -- a/Documentation/arm/keystone/knav-qmss.rst b/Documentation/arm/keystone/knav-qmss.rst
> --- a/Documentation/arm/keystone/knav-qmss.rst
> +++ b/Documentation/arm/keystone/knav-qmss.rst
> @@ -39,7 +39,7 @@ CPPI/QMSS Low Level Driver document (doc
>
> git://git.ti.com/keystone-rtos/qmss-lld.git
>
> -k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin firmware supports upto 48 accumulator
> +k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin firmware supports up to 48 accumulator
> channels. This firmware is available under ti-keystone folder of
> firmware.git at
>
> diff -- a/Documentation/arm/sunxi/clocks.rst b/Documentation/arm/sunxi/clocks.rst
> --- a/Documentation/arm/sunxi/clocks.rst
> +++ b/Documentation/arm/sunxi/clocks.rst
> @@ -5,7 +5,7 @@ Frequently asked questions about the sun
> This document contains useful bits of information that people tend to ask
> about the sunxi clock system, as well as accompanying ASCII art when adequate.
>
> -Q: Why is the main 24MHz oscillator gatable? Wouldn't that break the
> +Q: Why is the main 24MHz oscillator gateable? Wouldn't that break the
> system?
>
> A: The 24MHz oscillator allows gating to save power. Indeed, if gated
> diff -- a/Documentation/arm/vlocks.rst b/Documentation/arm/vlocks.rst
> --- a/Documentation/arm/vlocks.rst
> +++ b/Documentation/arm/vlocks.rst
> @@ -155,7 +155,7 @@ the basic algorithm:
> optimisation.
>
> If there are too many CPUs to read the currently_voting array in
> - one transaction then multiple transations are still required. The
> + one transaction then multiple transactions are still required. The
> implementation uses a simple loop of word-sized loads for this
> case. The number of transactions is still fewer than would be
> required if bytes were loaded individually.
>
Reviewed-by: Mukesh Ojha <quic_mojha@quicinc.com>
-Mukesh
> _______________________________________________
> 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:56 UTC|newest]
Thread overview: 78+ 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 ` [PATCH 02/35] Documentation: arm: correct spelling Randy Dunlap
2023-01-27 6:55 ` Mukesh Ojha [this message]
2023-01-27 6:39 ` [PATCH 01/35] Documentation: arm64: " Randy Dunlap
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 ` [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 ` [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 ` [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-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 7:05 ` Mukesh Ojha
2023-01-27 8:54 ` Daniel Bristot de Oliveira
2023-01-27 23:01 ` Randy Dunlap
2023-01-27 19:54 ` Steven Rostedt
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 20:30 ` patchwork-bot+netdevbpf
2023-01-31 16:28 ` (subset) " Catalin Marinas
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=3d99cf40-b5e2-21da-cc37-cd2e17ce10ad@quicinc.com \
--to=quic_mojha@quicinc.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=linux@armlinux.org.uk \
--cc=rdunlap@infradead.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).