From: Soham Metha <sohammetha01@gmail.com>
To: linux-doc@vger.kernel.org
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
skhan@linuxfoundation.org, corbet@lwn.net,
Soham Metha <sohammetha01@gmail.com>
Subject: [PATCH v2 8/9] docs: admin-guide: tainted-kernels: fixed spelling mistake in documentation
Date: Wed, 13 Aug 2025 02:31:50 +0530 [thread overview]
Message-ID: <20250812210150.74095-1-sohammetha01@gmail.com> (raw)
In-Reply-To: <20250812201523.69221-1-sohammetha01@gmail.com>
found/fixed the following typo
- userpace -> userspace
in `Documentation/admin-guide/tainted-kernels.rst`
Signed-off-by: Soham Metha <sohammetha01@gmail.com>
---
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 a0cc017e4424..ed1f8f1e86c5 100644
--- a/Documentation/admin-guide/tainted-kernels.rst
+++ b/Documentation/admin-guide/tainted-kernels.rst
@@ -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.34.1
next prev parent reply other threads:[~2025-08-12 21:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 20:15 [PATCH v2 0/9] docs: fix spelling mistakes across multiple directories Soham Metha
2025-08-12 20:15 ` [PATCH v2 1/9] docs: f2fs: fixed spelling mistakes in documentation Soham Metha
2025-08-13 3:13 ` Chao Yu
2025-08-12 20:49 ` [PATCH v2 3/9] docs: cgroup: " Soham Metha
2025-08-12 20:49 ` [PATCH v2 4/9] docs: device-mapper: " Soham Metha
2025-08-14 13:58 ` Mikulas Patocka
2025-08-12 20:49 ` [PATCH v2 5/9] docs: alienware-wmi: fixed spelling mistake in admin guide Soham Metha
2025-08-12 21:21 ` Kurt Borja
[not found] ` <dea5d89e-d918-4d80-a205-38ca7c166cc3@gmail.com>
[not found] ` <DC10RH2NVBR9.3QC7LKK4O4CW1@gmail.com>
2025-08-13 12:09 ` Soham Metha
2025-08-12 20:49 ` [PATCH v2 6/9] docs: damon: fixed spelling mistakes in documentation Soham Metha
2025-08-12 21:12 ` SeongJae Park
2025-08-12 20:49 ` [PATCH v2 7/9] docs: loongarch: fixed spelling mistake " Soham Metha
2025-08-12 20:52 ` [PATCH v2 3/9] docs: cgroup: fixed spelling mistakes " Tejun Heo
2025-08-12 21:01 ` Soham Metha [this message]
2025-08-12 21:04 ` [PATCH v2 9/9] docs: symbol-namespaces: fixed spelling mistake " Soham Metha
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=20250812210150.74095-1-sohammetha01@gmail.com \
--to=sohammetha01@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=skhan@linuxfoundation.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