[PATCH] docs: tainted-kernels: fix typos in documentation

Brian Knutsson posted 1 patch 2 months, 1 week ago
Documentation/admin-guide/tainted-kernels.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
[PATCH] docs: tainted-kernels: fix typos in documentation
Posted by Brian Knutsson 2 months, 1 week ago
Fix two minor typos in the tainted-kernels documentation:
- 'a more details explanation' -> 'a more detailed explanation'
- 'userpace' -> 'userspace'

Signed-off-by: Brian Knutsson <development@knutsson.it>
---
 Documentation/admin-guide/tainted-kernels.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/admin-guide/tainted-kernels.rst b/Documentation/admin-guide/tainted-kernels.rst
index a0cc017e4424..714186159536 100644
--- a/Documentation/admin-guide/tainted-kernels.rst
+++ b/Documentation/admin-guide/tainted-kernels.rst
@@ -63,7 +63,7 @@ this on the machine that had the statements in the logs that were quoted earlier
 	 * Externally-built ('out-of-tree') module was loaded  (#12)
 	See Documentation/admin-guide/tainted-kernels.rst in the Linux kernel or
 	 https://www.kernel.org/doc/html/latest/admin-guide/tainted-kernels.html for
-	 a more details explanation of the various taint flags.
+	 a more detailed explanation of the various taint flags.
 	Raw taint value as int/string: 4609/'P        W  O     '
 
 You can try to decode the number yourself. That's easy if there was only one
@@ -186,6 +186,6 @@ More detailed explanation for tainting
 
  18) ``N`` if an in-kernel test, such as a KUnit test, has been run.
 
- 19) ``J`` if userpace opened /dev/fwctl/* and performed a FWTCL_RPC_DEBUG_WRITE
+ 19) ``J`` if userspace opened /dev/fwctl/* and performed a FWTCL_RPC_DEBUG_WRITE
      to use the devices debugging features. Device debugging features could
      cause the device to malfunction in undefined ways.
-- 
2.48.1
Re: [PATCH] docs: tainted-kernels: fix typos in documentation
Posted by Randy Dunlap 2 months, 1 week ago

On 12/2/25 7:05 AM, Brian Knutsson wrote:
> Fix two minor typos in the tainted-kernels documentation:
> - 'a more details explanation' -> 'a more detailed explanation'
> - 'userpace' -> 'userspace'
> 
> Signed-off-by: Brian Knutsson <development@knutsson.it>

Acked-by: Randy Dunlap <rdunlap@infradead.org>

Thanks.

> ---
>  Documentation/admin-guide/tainted-kernels.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/admin-guide/tainted-kernels.rst b/Documentation/admin-guide/tainted-kernels.rst
> index a0cc017e4424..714186159536 100644
> --- a/Documentation/admin-guide/tainted-kernels.rst
> +++ b/Documentation/admin-guide/tainted-kernels.rst
> @@ -63,7 +63,7 @@ this on the machine that had the statements in the logs that were quoted earlier
>  	 * Externally-built ('out-of-tree') module was loaded  (#12)
>  	See Documentation/admin-guide/tainted-kernels.rst in the Linux kernel or
>  	 https://www.kernel.org/doc/html/latest/admin-guide/tainted-kernels.html for
> -	 a more details explanation of the various taint flags.
> +	 a more detailed explanation of the various taint flags.
>  	Raw taint value as int/string: 4609/'P        W  O     '
>  
>  You can try to decode the number yourself. That's easy if there was only one
> @@ -186,6 +186,6 @@ More detailed explanation for tainting
>  
>   18) ``N`` if an in-kernel test, such as a KUnit test, has been run.
>  
> - 19) ``J`` if userpace opened /dev/fwctl/* and performed a FWTCL_RPC_DEBUG_WRITE
> + 19) ``J`` if userspace opened /dev/fwctl/* and performed a FWTCL_RPC_DEBUG_WRITE
>       to use the devices debugging features. Device debugging features could
>       cause the device to malfunction in undefined ways.

-- 
~Randy