The patch titled
Subject: hfs: introduce VFS superblock object back-reference
has been removed from the -mm tree. Its filename was
hfs-introduce-vfs-superblock-object-back-reference.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Artem Bityutskiy <artem.bityutskiy@xxxxxxxxxxxxxxx>
Subject: hfs: introduce VFS superblock object back-reference
Add an 'sb' VFS superblock back-reference to the 'struct hfs_sb_info' data
structure - we will need to find the VFS superblock from a 'struct
hfs_sb_info' object in the next patch, so this change is jut a
preparation.
Remove few useless newlines while on it.
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@xxxxxxxxxxxxxxx>
Cc: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Cc: Christoph Hellwig <hch@xxxxxx>
Cc: Jan Kara <jack@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/hfs/hfs_fs.h | 6 +-----
fs/hfs/super.c | 1 +
2 files changed, 2 insertions(+), 5 deletions(-)
diff -puN fs/hfs/hfs_fs.h~hfs-introduce-vfs-superblock-object-back-reference fs/hfs/hfs_fs.h
--- a/fs/hfs/hfs_fs.h~hfs-introduce-vfs-superblock-object-back-reference
+++ a/fs/hfs/hfs_fs.h
@@ -137,16 +137,12 @@ struct hfs_sb_info {
gid_t s_gid; /* The gid of all files */
int session, part;
-
struct nls_table *nls_io, *nls_disk;
-
struct mutex bitmap_lock;
-
unsigned long flags;
-
u16 blockoffset;
-
int fs_div;
+ struct super_block *sb;
};
#define HFS_FLG_BITMAP_DIRTY 0
diff -puN fs/hfs/super.c~hfs-introduce-vfs-superblock-object-back-reference fs/hfs/super.c
--- a/fs/hfs/super.c~hfs-introduce-vfs-superblock-object-back-reference
+++ a/fs/hfs/super.c
@@ -380,6 +380,7 @@ static int hfs_fill_super(struct super_b
if (!sbi)
return -ENOMEM;
+ sbi->sb = sb;
sb->s_fs_info = sbi;
res = -EINVAL;
_
Patches currently in -mm which might be from artem.bityutskiy@xxxxxxxxxxxxxxx are
linux-next.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
