From: Brian Knutsson <development@knutsson.it>
To: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Knutsson Development <development@knutsson.it>
Subject: [PATCH] docs: tainted-kernels: fix typos in documentation
Date: Fri, 10 Apr 2026 16:56:06 +0200 [thread overview]
Message-ID: <20260410145606.774491-1-development@knutsson.it> (raw)
From: Knutsson Development <development@knutsson.it>
Fix two minor typos in the tainted-kernels documentation:
- 'a more details explanation' -> 'a more detailed explanation'
Signed-off-by: Knutsson Development <development@knutsson.it>
---
Documentation/admin-guide/tainted-kernels.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/tainted-kernels.rst b/Documentation/admin-guide/tainted-kernels.rst
index ed1f8f1e86c5..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
--
2.48.1
next reply other threads:[~2026-04-10 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 14:56 Brian Knutsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-02 15:05 [PATCH] docs: tainted-kernels: fix typos in documentation Brian Knutsson
2025-12-02 18:26 ` Randy Dunlap
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=20260410145606.774491-1-development@knutsson.it \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.