From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Filesystems Development <linux-fsdevel@vger.kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Christian Brauner <brauner@kernel.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>
Subject: [PATCH 5/5] Documentation: sharedsubtree: Convert notes to note directive
Date: Tue, 19 Aug 2025 13:12:53 +0700 [thread overview]
Message-ID: <20250819061254.31220-6-bagasdotme@gmail.com> (raw)
In-Reply-To: <20250819061254.31220-1-bagasdotme@gmail.com>
While a few of the notes are already in reST syntax, others are left
intact (inconsistent). Convert them to reST syntax too.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/filesystems/sharedsubtree.rst | 20 +++++++++++++-------
1 file changed, 13 insertions(+), 7 deletions(-)
diff --git a/Documentation/filesystems/sharedsubtree.rst b/Documentation/filesystems/sharedsubtree.rst
index b09650e285341c..8b7dc915908377 100644
--- a/Documentation/filesystems/sharedsubtree.rst
+++ b/Documentation/filesystems/sharedsubtree.rst
@@ -43,9 +43,10 @@ a) A **shared mount** can be replicated to as many mountpoints and all the
# mount --make-shared /mnt
- Note: mount(8) command now supports the --make-shared flag,
- so the sample 'smount' program is no longer needed and has been
- removed.
+ .. note::
+ mount(8) command now supports the --make-shared flag,
+ so the sample 'smount' program is no longer needed and has been
+ removed.
::
@@ -242,8 +243,9 @@ D) Versioned files
The section below explains the detailed semantics of
bind, rbind, move, mount, umount and clone-namespace operations.
-Note: the word 'vfsmount' and the noun 'mount' have been used
-to mean the same thing, throughout this document.
+.. Note::
+ the word 'vfsmount' and the noun 'mount' have been used
+ to mean the same thing, throughout this document.
a) Mount states
@@ -885,8 +887,12 @@ A) Datastructure
non-NULL, they form a contiguous (ordered) segment of slave list.
A example propagation tree looks as shown in the figure below.
- [ NOTE: Though it looks like a forest, if we consider all the shared
- mounts as a conceptual entity called 'pnode', it becomes a tree]::
+
+ .. note::
+ Though it looks like a forest, if we consider all the shared
+ mounts as a conceptual entity called 'pnode', it becomes a tree.
+
+ ::
A <--> B <--> C <---> D
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2025-08-19 6:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 6:12 [PATCH 0/5] Documentation: sharedsubtree: reST massaging Bagas Sanjaya
2025-08-19 6:12 ` [PATCH 1/5] Documentation: sharedsubtree: Format remaining of shell snippets as literal code blcoks Bagas Sanjaya
2025-08-19 6:12 ` [PATCH 2/5] Documentation: sharedsubtree: Use proper enumerator sequence for enumerated lists Bagas Sanjaya
2025-08-19 6:12 ` [PATCH 3/5] Documentation: sharedsubtree: Don't repeat lists with explanation Bagas Sanjaya
2025-08-19 6:12 ` [PATCH 4/5] Documentation: sharedsubtree: Align text Bagas Sanjaya
2025-08-19 6:12 ` Bagas Sanjaya [this message]
2025-08-29 22:41 ` [PATCH 0/5] Documentation: sharedsubtree: reST massaging Jonathan Corbet
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=20250819061254.31220-6-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®