linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Brian Knutsson <development@knutsson.it>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: tainted-kernels: fix typos in documentation
Date: Tue, 2 Dec 2025 10:26:38 -0800	[thread overview]
Message-ID: <b5ac862d-b369-497d-8968-8ee4a130d09a@infradead.org> (raw)
In-Reply-To: <20251202150534.885750-1-development@knutsson.it>



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

      reply	other threads:[~2025-12-02 18:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02 15:05 [PATCH] docs: tainted-kernels: fix typos in documentation Brian Knutsson
2025-12-02 18:26 ` Randy Dunlap [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b5ac862d-b369-497d-8968-8ee4a130d09a@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=development@knutsson.it \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).