Commit 78a00cac authored Jan 28, 2026 by Rhys Tumelty Committed by Jonathan Corbet Feb 02, 2026

docs: fix 're-use' -> 'reuse' in documentation



Signed-off-by: Rhys Tumelty <rhys@tumelty.co.uk>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Message-ID: <20260128220233.179439-1-rhys@tumelty.co.uk>

parent 1482f61c

Documentation/ABI/testing/pstore

+1 −1

Original line number	Diff line number	Diff line
		@@ -26,7 +26,7 @@ Description: Generic interface to platform dependent persistent storage.

		Once the information in a file has been read, removing
		the file will signal to the underlying persistent storage
		device that it can reclaim the space for later re-use::
		device that it can reclaim the space for later reuse::

		$ rm /sys/fs/pstore/dmesg-erst-1

Documentation/admin-guide/initrd.rst

+1 −1

Original line number	Diff line number	Diff line
		@@ -297,7 +297,7 @@ as follows:
		8) now the system is bootable and additional installation tasks can be
		performed

		The key role of initrd here is to re-use the configuration data during
		The key role of initrd here is to reuse the configuration data during
		normal system operation without requiring the use of a bloated "generic"
		kernel or re-compiling or re-linking the kernel.

Documentation/admin-guide/kdump/kdump.rst

+1 −1

Original line number	Diff line number	Diff line
		@@ -591,7 +591,7 @@ with /sys/kernel/config/crash_dm_crypt_keys for setup,
		cat /sys/kernel/config/crash_dm_crypt_keys/count
		2

		# To support CPU/memory hot-plugging, re-use keys already saved to reserved
		# To support CPU/memory hot-plugging, reuse keys already saved to reserved
		# memory
		echo true > /sys/kernel/config/crash_dm_crypt_key/reuse

Documentation/admin-guide/mm/nommu-mmap.rst

+1 −1

Original line number	Diff line number	Diff line
		@@ -38,7 +38,7 @@ and it's also much more restricted in the latter case:

		In the no-MMU case:

		- If one exists, the kernel will re-use an existing mapping to the
		- If one exists, the kernel will reuse an existing mapping to the
		same segment of the same file if that has compatible permissions,
		even if this was created by another process.

Documentation/arch/arm64/arm-acpi.rst

+2 −2

Original line number	Diff line number	Diff line
		@@ -306,9 +306,9 @@ that looks like this: Name(KEY0, "value0"). An ACPI device driver would
		then retrieve the value of the property by evaluating the KEY0 object.
		However, using Name() this way has multiple problems: (1) ACPI limits
		names ("KEY0") to four characters unlike DT; (2) there is no industry
		wide registry that maintains a list of names, minimizing re-use; (3)
		wide registry that maintains a list of names, minimizing reuse; (3)
		there is also no registry for the definition of property values ("value0"),
		again making re-use difficult; and (4) how does one maintain backward
		again making reuse difficult; and (4) how does one maintain backward
		compatibility as new hardware comes out? The _DSD method was created
		to solve precisely these sorts of problems; Linux drivers should ALWAYS
		use the _DSD method for device properties and nothing else.