From: Gleb Golovko <gaben123001@gmail.com>
To: linux-doc@vger.kernel.org
Cc: corbet@lwn.net, Gleb Golovko <gaben123001@gmail.com>
Subject: [PATCH] docs: fix duplicated word in real-time differences doc
Date: Thu, 9 Apr 2026 22:19:21 +0300 [thread overview]
Message-ID: <20260409191921.125-1-gaben123001@gmail.com> (raw)
Remove duplicated "the" in
Documentation/core-api/real-time/differences.rst.
Signed-off-by: Gleb Golovko <gaben123001@gmail.com>
---
Documentation/core-api/real-time/differences.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/core-api/real-time/differences.rst b/Documentation/core-api/real-time/differences.rst
index 83ec9aa1c61a..a129570dab5a 100644
--- a/Documentation/core-api/real-time/differences.rst
+++ b/Documentation/core-api/real-time/differences.rst
@@ -213,7 +213,7 @@ to suspend until the callback completes, ensuring forward progress without
risking livelock.
In order to solve the problem at the API level, the sequence locks were extended
-to allow a proper handover between the the spinning reader and the maybe
+to allow a proper handover between the spinning reader and the maybe
blocked writer.
Sequence locks
--
2.34.1
reply other threads:[~2026-04-09 19:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260409191921.125-1-gaben123001@gmail.com \
--to=gaben123001@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@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