public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tycho Andersen <tycho@tycho.ws>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Tycho Andersen <tycho@tycho.ws>
Subject: [PATCH] doc: fix filesystems/porting.rst whitespace
Date: Thu, 20 Feb 2020 14:40:09 -0700	[thread overview]
Message-ID: <20200220214009.11645-1-tycho@tycho.ws> (raw)

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@tycho.ws>
---
 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


             reply	other threads:[~2020-02-20 21:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20 21:40 Tycho Andersen [this message]
2020-02-25 10:20 ` [PATCH] doc: fix filesystems/porting.rst whitespace Jonathan Corbet
2020-02-25 16:59   ` Tycho Andersen
2020-02-26 11:21     ` Jonathan Corbet
2020-02-26 11:27     ` David Laight

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=20200220214009.11645-1-tycho@tycho.ws \
    --to=tycho@tycho.ws \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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