From: Hyeonjin Kim Date: Wed, 15 Apr 2026 00:12:04 +0000 (+0900) Subject: docs: fix typos in kernel documentation X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=8cfbcf36f97c5c9e70fe16c82a0f3782b8d67fe9;p=thirdparty%2Fkernel%2Flinux.git docs: fix typos in kernel documentation reinitalizes => reinitializes unpriviledged => unprivileged sub-struture => sub-structure Signed-off-by: Hyeonjin Kim Signed-off-by: Jonathan Corbet Message-ID: <20260415001204.6428-1-fruitworld.planet@gmail.com> --- diff --git a/Documentation/block/data-integrity.rst b/Documentation/block/data-integrity.rst index 99905e880a0e5..b7b10c8abbcc2 100644 --- a/Documentation/block/data-integrity.rst +++ b/Documentation/block/data-integrity.rst @@ -154,7 +154,7 @@ bio_free() will automatically free the bip. ---------------- Block devices can set up the integrity information in the integrity -sub-struture of the queue_limits structure. +sub-structure of the queue_limits structure. Layered block devices will need to pick a profile that's appropriate for all subdevices. queue_limits_stack_integrity() can help with that. DM diff --git a/Documentation/core-api/list.rst b/Documentation/core-api/list.rst index 241464ca05498..4819343a2706f 100644 --- a/Documentation/core-api/list.rst +++ b/Documentation/core-api/list.rst @@ -752,7 +752,7 @@ This is because list_splice() did not reinitialize the list_head it took entries from, leaving its pointer pointing into what is now a different list. If we want to avoid this situation, list_splice_init() can be used. It does the -same thing as list_splice(), except reinitalizes the donor list_head after the +same thing as list_splice(), except reinitializes the donor list_head after the transplant. Concurrency considerations diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst index 579e87cb9ff75..8717744f0fec0 100644 --- a/Documentation/gpu/drm-uapi.rst +++ b/Documentation/gpu/drm-uapi.rst @@ -568,7 +568,7 @@ ENOSPC: EPERM/EACCES: Returned for an operation that is valid, but needs more privileges. E.g. root-only or much more common, DRM master-only operations return - this when called by unpriviledged clients. There's no clear + this when called by unprivileged clients. There's no clear difference between EACCES and EPERM. ENODEV: