diff options
| author | Will Deacon <will.deacon@arm.com> | 2018-11-19 11:02:45 +0000 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2018-11-20 09:30:43 -0700 |
| commit | 806654a9667c6f60a65f1a4a4406082b5de51233 (patch) | |
| tree | 08b92f004840fb39bd563db58d0fb8bd5c6cc95a /Documentation/arm/Booting | |
| parent | 48c465d23d5ce55a84062e556e07a8a663349536 (diff) | |
| download | linux-806654a9667c6f60a65f1a4a4406082b5de51233.tar.bz2 | |
Documentation: Use "while" instead of "whilst"
Whilst making an unrelated change to some Documentation, Linus sayeth:
| Afaik, even in Britain, "whilst" is unusual and considered more
| formal, and "while" is the common word.
|
| [...]
|
| Can we just admit that we work with computers, and we don't need to
| use þe eald Englisc spelling of words that most of the world never
| uses?
dictionary.com refers to the word as "Chiefly British", which is
probably an undesirable attribute for technical documentation.
Replace all occurrences under Documentation/ with "while".
Cc: David Howells <dhowells@redhat.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Michael Halcrow <mhalcrow@google.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Reported-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/arm/Booting')
| -rw-r--r-- | Documentation/arm/Booting | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/arm/Booting b/Documentation/arm/Booting index 259f00af3ab3..f1f965ce93d6 100644 --- a/Documentation/arm/Booting +++ b/Documentation/arm/Booting @@ -126,7 +126,7 @@ tagged list. The boot loader must pass at a minimum the size and location of the system memory, and the root filesystem location. The dtb must be placed in a region of memory where the kernel decompressor will not -overwrite it, whilst remaining within the region which will be covered +overwrite it, while remaining within the region which will be covered by the kernel's low-memory mapping. A safe location is just above the 128MiB boundary from start of RAM. |