If we start with spaces instead of tabs, rst seems to get confused and
italicize some things (presumably because of the `*'s).
Instead, let's switch to using leading tabs as we do elsewhere in the file.
Signed-off-by: Tycho Andersen <tycho@xxxxxxxx>
---
Documentation/filesystems/porting.rst | 21 +++++++++++----------
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/Documentation/filesystems/porting.rst b/Documentation/filesystems/porting.rst
index f18506083ced..898e1d0c6e98 100644
--- a/Documentation/filesystems/porting.rst
+++ b/Documentation/filesystems/porting.rst
@@ -57,12 +57,13 @@ Turn your foo_read_super() into a function that would return 0 in case of
success and negative number in case of error (-EINVAL unless you have more
informative error value to report). Call it foo_fill_super(). Now declare::
- int foo_get_sb(struct file_system_type *fs_type,
- int flags, const char *dev_name, void *data, struct vfsmount *mnt)
- {
- return get_sb_bdev(fs_type, flags, dev_name, data, foo_fill_super,
- mnt);
- }
+ int foo_get_sb(struct file_system_type *fs_type,
+ int flags, const char *dev_name, void *data,
+ struct vfsmount *mnt)
+ {
+ return get_sb_bdev(fs_type, flags, dev_name, data, foo_fill_super,
+ mnt);
+ }
(or similar with s/bdev/nodev/ or s/bdev/single/, depending on the kind of
filesystem).
@@ -181,10 +182,10 @@ can be used as examples of very different filesystems.
iget4() and the read_inode2 callback have been superseded by iget5_locked()
which has the following prototype::
- struct inode *iget5_locked(struct super_block *sb, unsigned long ino,
- int (*test)(struct inode *, void *),
- int (*set)(struct inode *, void *),
- void *data);
+ struct inode *iget5_locked(struct super_block *sb, unsigned long ino,
+ int (*test)(struct inode *, void *),
+ int (*set)(struct inode *, void *),
+ void *data);
'test' is an additional function that can be used when the inode
number is not sufficient to identify the actual file object. 'set'
--
2.20.1
