From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Akinobu Mita <akinobu.mita@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: [PATCH 04/24] Documentation: fault-injection: correct spelling
Date: Wed, 8 Feb 2023 23:13:40 -0800 [thread overview]
Message-ID: <20230209071400.31476-5-rdunlap@infradead.org> (raw)
In-Reply-To: <20230209071400.31476-1-rdunlap@infradead.org>
Correct spelling problems for Documentation/fault-injection/ as reported
by codespell.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Akinobu Mita <akinobu.mita@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
---
Documentation/fault-injection/fault-injection.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -- a/Documentation/fault-injection/fault-injection.rst b/Documentation/fault-injection/fault-injection.rst
--- a/Documentation/fault-injection/fault-injection.rst
+++ b/Documentation/fault-injection/fault-injection.rst
@@ -235,7 +235,7 @@ proc entries
Error Injectable Functions
--------------------------
-This part is for the kenrel developers considering to add a function to
+This part is for the kernel developers considering to add a function to
ALLOW_ERROR_INJECTION() macro.
Requirements for the Error Injectable Functions
next prev parent reply other threads:[~2023-02-09 7:14 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 7:13 [PATCH 00/24 v2] Documentation: correct lots of spelling errors (series 1) Randy Dunlap
2023-02-09 7:13 ` [PATCH 01/24] Documentation: arm: correct spelling Randy Dunlap
2023-02-09 7:13 ` [PATCH 02/24] Documentation: block: " Randy Dunlap
2023-02-09 7:13 ` [PATCH 03/24] Documentation: core-api: " Randy Dunlap
2023-02-09 15:20 ` Daniel Jordan
2023-02-11 0:26 ` Jakub Kicinski
2023-02-09 7:13 ` Randy Dunlap [this message]
2023-02-09 7:13 ` [PATCH 05/24] Documentation: fb: " Randy Dunlap
2023-02-09 7:13 ` [PATCH 06/24] Documentation: features: " Randy Dunlap
2023-02-09 7:13 ` [PATCH 07/24] Documentation: input: " Randy Dunlap
2023-02-09 7:13 ` [PATCH 08/24] Documentation: isdn: " Randy Dunlap
2023-02-09 7:13 ` [PATCH 09/24] Documentation: livepatch: " Randy Dunlap
2023-02-09 7:13 ` [PATCH 10/24] Documentation: locking: " Randy Dunlap
2023-02-09 7:13 ` [PATCH 11/24] Documentation: mm: " Randy Dunlap
2023-02-09 7:13 ` [PATCH 12/24] Documentation: openrisc: " Randy Dunlap
2023-02-09 7:13 ` [PATCH 13/24] Documentation: PCI: " Randy Dunlap
2023-02-09 7:13 ` [PATCH 14/24] Documentation: powerpc: " Randy Dunlap
2023-02-09 7:13 ` [PATCH 15/24] Documentation: s390: " Randy Dunlap
2023-02-09 20:13 ` Heiko Carstens
2023-02-09 7:13 ` [PATCH 16/24] Documentation: scheduler: " Randy Dunlap
2023-02-09 9:20 ` Vincent Guittot
2023-02-09 7:13 ` [PATCH 17/24] Documentation: security: " Randy Dunlap
2023-02-10 3:54 ` Jarkko Sakkinen
2023-02-10 3:55 ` Jarkko Sakkinen
2023-02-09 7:13 ` [PATCH 18/24] Documentation: timers: " Randy Dunlap
2023-02-09 7:13 ` [PATCH 19/24] Documentation: tools/rtla: " Randy Dunlap
2023-02-10 21:37 ` Steven Rostedt
2023-02-09 7:13 ` [PATCH 20/24] Documentation: trace/rv: " Randy Dunlap
2023-02-09 11:45 ` Daniel Bristot de Oliveira
2023-02-10 21:37 ` Steven Rostedt
2023-02-09 7:13 ` [PATCH 21/24] Documentation: trace: " Randy Dunlap
2023-02-09 11:40 ` Mike Leach
2023-02-09 11:46 ` Daniel Bristot de Oliveira
2023-02-09 14:41 ` Masami Hiramatsu
2023-02-10 21:39 ` Steven Rostedt
2023-02-09 7:13 ` [PATCH 22/24] Documentation: w1: " Randy Dunlap
2023-02-09 7:13 ` [PATCH 23/24] Documentation: x86: " Randy Dunlap
2023-02-09 23:22 ` Reinette Chatre
2023-02-10 3:55 ` Jarkko Sakkinen
2023-02-14 1:23 ` Huang, Kai
2023-02-10 4:19 ` Fenghua Yu
2023-02-09 7:14 ` [PATCH 24/24] Documentation: xtensa: " Randy Dunlap
2023-02-11 0:30 ` [PATCH 00/24 v2] Documentation: correct lots of spelling errors (series 1) patchwork-bot+netdevbpf
2023-06-26 6:56 ` Krzysztof Wilczyński
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=20230209071400.31476-5-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=akinobu.mita@gmail.com \
--cc=corbet@lwn.net \
--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).