Linux Documentation
 help / color / mirror / Atom feed
From: Alexander Aring <aahringo@redhat.com>
To: corbet@lwn.net
Cc: linux-doc@vger.kernel.org, aahringo@redhat.com
Subject: [PATCH] Documentation: locking: fix references
Date: Mon, 23 Aug 2021 13:15:46 -0400	[thread overview]
Message-ID: <20210823171546.1686907-1-aahringo@redhat.com> (raw)

This patch fixes file references from txt to rst file ending in
ww-mutex-design.rst and futex-requeue-pi.rst.

Signed-off-by: Alexander Aring <aahringo@redhat.com>
---
Maybe there are more somewhere else in Documentation? However I caught
these ones in locking.

 Documentation/locking/futex-requeue-pi.rst | 2 +-
 Documentation/locking/ww-mutex-design.rst  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/locking/futex-requeue-pi.rst b/Documentation/locking/futex-requeue-pi.rst
index 14ab5787b9a7..27c7a2b8966f 100644
--- a/Documentation/locking/futex-requeue-pi.rst
+++ b/Documentation/locking/futex-requeue-pi.rst
@@ -5,7 +5,7 @@ Futex Requeue PI
 Requeueing of tasks from a non-PI futex to a PI futex requires
 special handling in order to ensure the underlying rt_mutex is never
 left without an owner if it has waiters; doing so would break the PI
-boosting logic [see rt-mutex-desgin.txt] For the purposes of
+boosting logic [see rt-mutex-desgin.rst] For the purposes of
 brevity, this action will be referred to as "requeue_pi" throughout
 this document.  Priority inheritance is abbreviated throughout as
 "PI".
diff --git a/Documentation/locking/ww-mutex-design.rst b/Documentation/locking/ww-mutex-design.rst
index 54d9c17bb66b..6a4d7319f8f0 100644
--- a/Documentation/locking/ww-mutex-design.rst
+++ b/Documentation/locking/ww-mutex-design.rst
@@ -2,7 +2,7 @@
 Wound/Wait Deadlock-Proof Mutex Design
 ======================================
 
-Please read mutex-design.txt first, as it applies to wait/wound mutexes too.
+Please read mutex-design.rst first, as it applies to wait/wound mutexes too.
 
 Motivation for WW-Mutexes
 -------------------------
-- 
2.27.0


             reply	other threads:[~2021-08-23 17:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 17:15 Alexander Aring [this message]
2021-08-23 17:37 ` [PATCH] Documentation: locking: fix references Matthew Wilcox
2021-08-23 18:25   ` Alexander Aring

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=20210823171546.1686907-1-aahringo@redhat.com \
    --to=aahringo@redhat.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