All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sachidananda Urs <sacchi@gmail.com>
To: Rob Landley <rob@landley.net>, Al Viro <viro@zeniv.linux.org.uk>,
	Fengguang Wu <fengguang.wu@intel.com>, Jan Kara <jack@suse.cz>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Sachidananda Urs <sacchi@gmail.com>
Subject: [PATCH] Documentation/filesystems/porting: Update documentation.
Date: Fri,  3 Aug 2012 23:04:25 +0530	[thread overview]
Message-ID: <1344015265-6752-1-git-send-email-sacchi@gmail.com> (raw)

->get_sb() is no longer used, update documentation to use ->mount(). Also added
  a example for struct file_system_type.

Signed-off-by: Sachidananda Urs <sacchi@gmail.com>
---
 Documentation/filesystems/porting |   20 +++++++++++++-------
 1 files changed, 13 insertions(+), 7 deletions(-)

diff --git a/Documentation/filesystems/porting b/Documentation/filesystems/porting
index 2bef2b3..d6d53fb 100644
--- a/Documentation/filesystems/porting
+++ b/Documentation/filesystems/porting
@@ -42,26 +42,32 @@ At some point that will become mandatory.
 ---
 [mandatory]
 
-Change of file_system_type method (->read_super to ->get_sb)
+Change of file_system_type method (->read_super to ->get_sb to ->mount)
 
-->read_super() is no more.  Ditto for DECLARE_FSTYPE and DECLARE_FSTYPE_DEV.
+->read_super() is no more and so is ->get_sb.  Ditto for DECLARE_FSTYPE and
+  DECLARE_FSTYPE_DEV.
 
 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)
+static struct dentry *foo_mount(struct file_system_type *fs_type, int flags,
+                                const char *dev_name, void *data)
 {
-	return get_sb_bdev(fs_type, flags, dev_name, data, foo_fill_super,
-			   mnt);
+        return mount_bdev(fs_type, flags, dev_name, data, foo_fill_super);
 }
 
 (or similar with s/bdev/nodev/ or s/bdev/single/, depending on the kind of
 filesystem).
 
 Replace DECLARE_FSTYPE... with explicit initializer and have ->get_sb set as
-foo_get_sb.
+foo_mount. For example:
+
+static struct file_system_type foo_fs_type = {
+        .owner  = THIS_MODULE,
+        .name   = "foo",
+        .mount  = foo_mount,
+};
 
 ---
 [mandatory]
-- 
1.7.7.6


             reply	other threads:[~2012-08-03 17:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-03 17:34 Sachidananda Urs [this message]
2012-08-05 20:54 ` [PATCH] Documentation/filesystems/porting: Update documentation Rob Landley
  -- strict thread matches above, loose matches on Subject: below --
2012-08-03 14:17 Sachidananda Urs
2012-08-03 17:05 ` Vijay Bellur

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=1344015265-6752-1-git-send-email-sacchi@gmail.com \
    --to=sacchi@gmail.com \
    --cc=fengguang.wu@intel.com \
    --cc=jack@suse.cz \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.