[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241120055246.158368-1-rdunlap@infradead.org>
Date: Tue, 19 Nov 2024 21:52:46 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: linux-kernel@...r.kernel.org
Cc: Randy Dunlap <rdunlap@...radead.org>,
Jonathan Corbet <corbet@....net>,
linux-doc@...r.kernel.org,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>,
Jan Kara <jack@...e.cz>,
linux-fsdevel@...r.kernel.org,
Ian Kent <raven@...maw.net>,
autofs@...r.kernel.org,
Alexander Aring <aahringo@...hat.com>,
David Teigland <teigland@...hat.com>,
gfs2@...ts.linux.dev,
Eric Biggers <ebiggers@...nel.org>,
"Theodore Y. Ts'o" <tytso@....edu>,
fsverity@...ts.linux.dev,
Mark Fasheh <mark@...heh.com>,
Joel Becker <jlbec@...lplan.org>,
Joseph Qi <joseph.qi@...ux.alibaba.com>,
ocfs2-devel@...ts.linux.dev
Subject: [PATCH] Documentation: filesystems: update filename extensions
Update references to most txt files to rst files.
Update one reference to an md file to a rst file.
Update one file path to its current location.
Signed-off-by: Randy Dunlap <rdunlap@...radead.org>
Cc: Jonathan Corbet <corbet@....net>
Cc: linux-doc@...r.kernel.org
Cc: Alexander Viro <viro@...iv.linux.org.uk>
Cc: Christian Brauner <brauner@...nel.org>
Cc: Jan Kara <jack@...e.cz>
Cc: linux-fsdevel@...r.kernel.org
Cc: Ian Kent <raven@...maw.net>
Cc: autofs@...r.kernel.org
Cc: Alexander Aring <aahringo@...hat.com>
Cc: David Teigland <teigland@...hat.com>
Cc: gfs2@...ts.linux.dev
Cc: Eric Biggers <ebiggers@...nel.org>
Cc: Theodore Y. Ts'o <tytso@....edu>
Cc: fsverity@...ts.linux.dev
Cc: Mark Fasheh <mark@...heh.com>
Cc: Joel Becker <jlbec@...lplan.org>
Cc: Joseph Qi <joseph.qi@...ux.alibaba.com>
Cc: ocfs2-devel@...ts.linux.dev
---
Documentation/filesystems/autofs.rst | 2 +-
Documentation/filesystems/dlmfs.rst | 2 +-
Documentation/filesystems/fsverity.rst | 2 +-
Documentation/filesystems/path-lookup.rst | 2 +-
Documentation/filesystems/path-lookup.txt | 2 +-
Documentation/filesystems/ramfs-rootfs-initramfs.rst | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
--- linux-next-20241119.orig/Documentation/filesystems/autofs.rst
+++ linux-next-20241119/Documentation/filesystems/autofs.rst
@@ -442,7 +442,7 @@ which can be used to communicate directl
It requires CAP_SYS_ADMIN for access.
The 'ioctl's that can be used on this device are described in a separate
-document `autofs-mount-control.txt`, and are summarised briefly here.
+document `autofs-mount-control.rst`, and are summarised briefly here.
Each ioctl is passed a pointer to an `autofs_dev_ioctl` structure::
struct autofs_dev_ioctl {
--- linux-next-20241119.orig/Documentation/filesystems/dlmfs.rst
+++ linux-next-20241119/Documentation/filesystems/dlmfs.rst
@@ -36,7 +36,7 @@ None
Usage
=====
-If you're just interested in OCFS2, then please see ocfs2.txt. The
+If you're just interested in OCFS2, then please see ocfs2.rst. The
rest of this document will be geared towards those who want to use
dlmfs for easy to setup and easy to use clustered locking in
userspace.
--- linux-next-20241119.orig/Documentation/filesystems/fsverity.rst
+++ linux-next-20241119/Documentation/filesystems/fsverity.rst
@@ -16,7 +16,7 @@ btrfs filesystems. Like fscrypt, not to
code is needed to support fs-verity.
fs-verity is similar to `dm-verity
-<https://www.kernel.org/doc/Documentation/device-mapper/verity.txt>`_
+<https://www.kernel.org/doc/Documentation/admin-guide/device-mapper/verity.rst>`_
but works on files rather than block devices. On regular files on
filesystems supporting fs-verity, userspace can execute an ioctl that
causes the filesystem to build a Merkle tree for the file and persist
--- linux-next-20241119.orig/Documentation/filesystems/path-lookup.rst
+++ linux-next-20241119/Documentation/filesystems/path-lookup.rst
@@ -531,7 +531,7 @@ this retry process in the next article.
Automount points are locations in the filesystem where an attempt to
lookup a name can trigger changes to how that lookup should be
handled, in particular by mounting a filesystem there. These are
-covered in greater detail in autofs.txt in the Linux documentation
+covered in greater detail in autofs.rst in the Linux documentation
tree, but a few notes specifically related to path lookup are in order
here.
--- linux-next-20241119.orig/Documentation/filesystems/ramfs-rootfs-initramfs.rst
+++ linux-next-20241119/Documentation/filesystems/ramfs-rootfs-initramfs.rst
@@ -315,7 +315,7 @@ the above threads) is:
2) The cpio archive format chosen by the kernel is simpler and cleaner (and
thus easier to create and parse) than any of the (literally dozens of)
various tar archive formats. The complete initramfs archive format is
- explained in buffer-format.txt, created in usr/gen_init_cpio.c, and
+ explained in buffer-format.rst, created in usr/gen_init_cpio.c, and
extracted in init/initramfs.c. All three together come to less than 26k
total of human-readable text.
--- linux-next-20241119.orig/Documentation/filesystems/path-lookup.txt
+++ linux-next-20241119/Documentation/filesystems/path-lookup.txt
@@ -379,4 +379,4 @@ Papers and other documentation on dcache
2. http://lse.sourceforge.net/locking/dcache/dcache.html
-3. path-lookup.md in this directory.
+3. path-lookup.rst in this directory.
Powered by blists - more mailing lists