archive mirror
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <>
To: Jonathan Corbet <>
Cc: "Tobin C. Harding" <>,,,
Subject: [PATCH 04/13] docs: filesystems: vfs: Use uniform spacing around headings
Date: Wed, 13 Mar 2019 15:09:10 +1100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Currently spacing before and after headings is non-uniform.  Use two
blank lines before a heading and one after the heading.

Use uniform spacing around headings.

Signed-off-by: Tobin C. Harding <>
 Documentation/filesystems/vfs.txt | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/Documentation/filesystems/vfs.txt b/Documentation/filesystems/vfs.txt
index 5c4d74547dd7..b452b3fc5edc 100644
--- a/Documentation/filesystems/vfs.txt
+++ b/Documentation/filesystems/vfs.txt
@@ -321,6 +321,7 @@ Whoever sets up the inode is responsible for filling in the "i_op"
 field.  This is a pointer to a "struct inode_operations" which describes
 the methods that can be performed on individual inodes.
 struct xattr_handlers
@@ -507,6 +508,7 @@ otherwise noted.
   tmpfile: called in the end of O_TMPFILE open().  Optional, equivalent to
 	atomically creating, opening and unlinking a file in given directory.
 The Address Space Object
@@ -580,8 +582,10 @@ and the constraints under which it is being done.  It is also used to
 return information back to the caller about the result of a writepage or
 writepages request.
 Handling errors during writeback
 Most applications that do buffered I/O will periodically call a file
 synchronization call (fsync, fdatasync, msync or sync_file_range) to
 ensure that data written has made it to the backing store.  When there
@@ -612,6 +616,7 @@ file->fsync operation, they should call file_check_and_advance_wb_err to
 ensure that the struct file's error cursor has advanced to the correct
 point in the stream of errors emitted by the backing device(s).
 struct address_space_operations
@@ -1200,9 +1205,11 @@ manipulate dentries:
 	and the dentry is returned.  The caller must use dput()
 	to free the dentry when it finishes using it.
 Mount Options
 Parsing options
@@ -1217,6 +1224,7 @@ The <linux/parser.h> header defines an API that helps parse these
 options.  There are plenty of examples on how to use it in existing
 Showing options
@@ -1238,6 +1246,7 @@ The underlying reason for the above rules is to make sure, that a mount
 can be accurately replicated (e.g. umounting and mounting again) based
 on the information found in /proc/mounts.

  parent reply	other threads:[~2019-03-13  4:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13  4:09 [PATCH 00/13] Convert vfs.txt to vfs.rst Tobin C. Harding
2019-03-13  4:09 ` [PATCH 01/13] docs: filesystems: vfs: Remove space before tab Tobin C. Harding
2019-03-13  4:09 ` [PATCH 02/13] docs: filesystems: vfs: Use uniform space after period Tobin C. Harding
2019-03-13  4:09 ` [PATCH 03/13] docs: filesystems: vfs: Use 72 character column width Tobin C. Harding
2019-03-13  4:09 ` Tobin C. Harding [this message]
2019-03-13  4:09 ` [PATCH 05/13] docs: filesystems: vfs: Use correct initial heading Tobin C. Harding
2019-03-13  4:09 ` [PATCH 06/13] docs: filesystems: vfs: Use SPDX identifier Tobin C. Harding
2019-03-13  4:09 ` [PATCH 07/13] docs: filesystems: vfs: Fix pre-amble indentation Tobin C. Harding
2019-03-13  4:09 ` [PATCH 08/13] docs: filesystems: vfs: Use list character for lists Tobin C. Harding
2019-03-13  4:09 ` [PATCH 09/13] docs: filesystems: vfs: Add code-block and txt->RST Tobin C. Harding
2019-03-13  4:09 ` [PATCH 10/13] docs: filesystems: vfs: Use ticks for listed items Tobin C. Harding
2019-03-13  4:09 ` [PATCH 11/13] docs: filesystems: vfs: Clean up lists Tobin C. Harding
2019-03-13  4:09 ` [PATCH 12/13] docs: filesystems: vfs: Do minor grammar fixes Tobin C. Harding
2019-03-13  4:09 ` [PATCH 13/13] docs: filesystems: vfs: Use backticks to guard star Tobin C. Harding
2019-03-18  1:46 ` [PATCH 00/13] Convert vfs.txt to vfs.rst Randy Dunlap
2019-03-18  3:34   ` Tobin C. Harding
2019-03-18 17:42     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).