From: Akiyoshi Kurita <weibu@redadmin.org>
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Cc: Dave Jiang <dave.jiang@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Shannon Nelson <sln@onemain.com>, Jason Gunthorpe <jgg@ziepe.ca>,
linux-kernel@vger.kernel.org,
Akiyoshi Kurita <weibu@redadmin.org>
Subject: [PATCH] Documentation: admin-guide: Correct spelling of "userspace"
Date: Sat, 27 Sep 2025 04:00:19 +0900 [thread overview]
Message-ID: <20250926190019.41788-1-weibu@redadmin.org> (raw)
The term "userspace" should be a single word. Fix the typo
"userpace" accordingly.
Signed-off-by: Akiyoshi Kurita <weibu@redadmin.org>
---
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.47.3
next reply other threads:[~2025-09-26 19:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 19:00 Akiyoshi Kurita [this message]
2025-09-26 20:40 ` [PATCH] Documentation: admin-guide: Correct spelling of "userspace" Dave Jiang
2025-10-14 14:57 ` Jonathan Corbet
2025-10-14 17:59 ` Randy Dunlap
2025-10-14 18:22 ` Jonathan Corbet
2025-10-14 18:39 ` Randy Dunlap
[not found] <1760540376-6149-mlmmj-2f9fba2d@vger.kernel.org>
2025-10-15 15:21 ` weibu
2025-10-15 16:34 ` 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=20250926190019.41788-1-weibu@redadmin.org \
--to=weibu@redadmin.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=corbet@lwn.net \
--cc=dave.jiang@intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sln@onemain.com \
/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).