]> git.ipfire.org Git - thirdparty/linux.git/commitdiff
docs/vfs: Remove mentions to the old mount API helpers
authorPedro Falcato <pfalcato@suse.de>
Wed, 23 Jul 2025 13:21:56 +0000 (14:21 +0100)
committerChristian Brauner <brauner@kernel.org>
Mon, 11 Aug 2025 12:52:40 +0000 (14:52 +0200)
Now that mount_bdev(), mount_nodev() and mount_single() have all been
removed, remove mentions to them in vfs.rst.

While we're at it, redirect people looking for mount API docs to
mount_api.rst (which documents the newer API).

Signed-off-by: Pedro Falcato <pfalcato@suse.de>
Link: https://lore.kernel.org/20250723132156.225410-4-pfalcato@suse.de
Signed-off-by: Christian Brauner <brauner@kernel.org>
Documentation/filesystems/vfs.rst

index 486a9163347478f0fb4c0938dec4cb3509f8afd5..229eb90c96f2a9e7b096cb6d1d9e8352db3e739f 100644 (file)
@@ -209,31 +209,8 @@ method fills in is the "s_op" field.  This is a pointer to a "struct
 super_operations" which describes the next level of the filesystem
 implementation.
 
-Usually, a filesystem uses one of the generic mount() implementations
-and provides a fill_super() callback instead.  The generic variants are:
-
-``mount_bdev``
-       mount a filesystem residing on a block device
-
-``mount_nodev``
-       mount a filesystem that is not backed by a device
-
-``mount_single``
-       mount a filesystem which shares the instance between all mounts
-
-A fill_super() callback implementation has the following arguments:
-
-``struct super_block *sb``
-       the superblock structure.  The callback must initialize this
-       properly.
-
-``void *data``
-       arbitrary mount options, usually comes as an ASCII string (see
-       "Mount Options" section)
-
-``int silent``
-       whether or not to be silent on error
-
+For more information on mounting (and the new mount API), see
+Documentation/filesystems/mount_api.rst.
 
 The Superblock Object
 =====================