docs: fix typos in kernel documentation
Subsystems (5)
PATCH 1/1 docs: fix typos in kernel documentation
reinitalizes => reinitializes
unpriviledged => unprivileged
the the => the (duplicated word)
sub-struture => sub-structure
--- Documentation/block/data-integrity.rst | 2 +- Documentation/core-api/list.rst | 2 +- Documentation/core-api/real-time/differences.rst | 2 +- Documentation/gpu/drm-uapi.rst | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-)
Documentation/block/data-integrity.rst +1 -1
@@ -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
Documentation/core-api/list.rst +1 -1
@@ -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
Documentation/core-api/real-time/differences.rst +1 -1
@@ -213,7 +213,7 @@ to suspend until the callback completes, ensuring forward progress without risking livelock. In order to solve the problem at the API level, the sequence locks were extended -to allow a proper handover between the the spinning reader and the maybe +to allow a proper handover between the spinning reader and the maybe blocked writer. Sequence locks
Documentation/gpu/drm-uapi.rst +1 -1
@@ -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:
Signature · 1 line
2.52.0
Jonathan Corbet
maintainerThank you for working to improve our documentation.
Quoted 4 lines · fru1tworld <[email protected]> writes:
reinitalizes => reinitializes
unpriviledged => unprivileged
the the => the (duplicated word)
sub-struture => sub-structure
These changes generally look OK, but...
Quoted 1 line
Signed-off-by fru1tworld <[email protected]>
We need a proper signoff with your real name, please.
Quoted 4 lines
--- Documentation/block/data-integrity.rst | 2 +- Documentation/core-api/list.rst | 2 +- Documentation/core-api/real-time/differences.rst | 2 +-
This one has already been fixed; it's always best to prepare your patches against docs-next or linux-next.
Quoted 2 lines
Documentation/gpu/drm-uapi.rst | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-)
Thanks,
jon
PATCH v2 1/1 docs: fix typos in kernel documentation
In reply to fru1tworldFrom: Hyeonjin Kim <[email protected]>
reinitalizes => reinitializes
unpriviledged => unprivileged
sub-struture => sub-structure
--- Documentation/block/data-integrity.rst | 2 +- Documentation/core-api/list.rst | 2 +- Documentation/gpu/drm-uapi.rst | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
Documentation/block/data-integrity.rst +1 -1
@@ -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
Documentation/core-api/list.rst +1 -1
@@ -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
Documentation/gpu/drm-uapi.rst +1 -1
@@ -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:
Signature · 1 line
2.52.0
Quoted 6 lines · fru1tworld <[email protected]> writes:
From: Hyeonjin Kim <[email protected]>
reinitalizes => reinitializes
unpriviledged => unprivileged
sub-struture => sub-structure
Quoted 6 lines
Signed-off-by Hyeonjin Kim <[email protected]>--- Documentation/block/data-integrity.rst | 2 +- Documentation/core-api/list.rst | 2 +- Documentation/gpu/drm-uapi.rst | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
Applied, thanks.
jon