Commit 166ac34b authored by Artem Bityutskiy's avatar Artem Bityutskiy Committed by Al Viro

nilfs2: nuke write_super from comments

The '->write_super' superblock method is gone, and this patch removes all the
references to 'write_super' from ntfs.

Cc: KONISHI Ryusuke <konishi.ryusuke@lab.ntt.co.jp>
Signed-off-by: default avatarArtem Bityutskiy <artem.bityutskiy@linux.intel.com>
Signed-off-by: default avatarAl Viro <viro@zeniv.linux.org.uk>
parent 50640bcc
...@@ -676,17 +676,13 @@ static const struct super_operations nilfs_sops = { ...@@ -676,17 +676,13 @@ static const struct super_operations nilfs_sops = {
.alloc_inode = nilfs_alloc_inode, .alloc_inode = nilfs_alloc_inode,
.destroy_inode = nilfs_destroy_inode, .destroy_inode = nilfs_destroy_inode,
.dirty_inode = nilfs_dirty_inode, .dirty_inode = nilfs_dirty_inode,
/* .write_inode = nilfs_write_inode, */
/* .drop_inode = nilfs_drop_inode, */
.evict_inode = nilfs_evict_inode, .evict_inode = nilfs_evict_inode,
.put_super = nilfs_put_super, .put_super = nilfs_put_super,
/* .write_super = nilfs_write_super, */
.sync_fs = nilfs_sync_fs, .sync_fs = nilfs_sync_fs,
.freeze_fs = nilfs_freeze, .freeze_fs = nilfs_freeze,
.unfreeze_fs = nilfs_unfreeze, .unfreeze_fs = nilfs_unfreeze,
.statfs = nilfs_statfs, .statfs = nilfs_statfs,
.remount_fs = nilfs_remount, .remount_fs = nilfs_remount,
/* .umount_begin */
.show_options = nilfs_show_options .show_options = nilfs_show_options
}; };
......
...@@ -107,8 +107,6 @@ struct the_nilfs { ...@@ -107,8 +107,6 @@ struct the_nilfs {
* used for * used for
* - loading the latest checkpoint exclusively. * - loading the latest checkpoint exclusively.
* - allocating a new full segment. * - allocating a new full segment.
* - protecting s_dirt in the super_block struct
* (see nilfs_write_super) and the following fields.
*/ */
struct buffer_head *ns_sbh[2]; struct buffer_head *ns_sbh[2];
struct nilfs_super_block *ns_sbp[2]; struct nilfs_super_block *ns_sbp[2];
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment