Message ID | 1550857192-10513-5-git-send-email-anand.jain@oracle.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | Misc props.c cleanups | expand |
On Sat, Feb 23, 2019 at 01:39:46AM +0800, Anand Jain wrote: > fs_info is commonly used to represent struct fs_info *, rename > to fs_private to avoid confusion. Yeah, I had the same thoughts. The parameter name in interface function security_inode_init_security is fs_data, I think we can use that name too. Reviewed-by: David Sterba <dsterba@suse.com>
diff --git a/fs/btrfs/xattr.c b/fs/btrfs/xattr.c index 499bb79ba135..6971cbf286b5 100644 --- a/fs/btrfs/xattr.c +++ b/fs/btrfs/xattr.c @@ -419,10 +419,10 @@ static int btrfs_xattr_handler_set_prop(const struct xattr_handler *handler, }; static int btrfs_initxattrs(struct inode *inode, - const struct xattr *xattr_array, void *fs_info) + const struct xattr *xattr_array, void *fs_private) { + struct btrfs_trans_handle *trans = fs_private; const struct xattr *xattr; - struct btrfs_trans_handle *trans = fs_info; unsigned int nofs_flag; char *name; int err = 0;
fs_info is commonly used to represent struct fs_info *, rename to fs_private to avoid confusion. Signed-off-by: Anand Jain <anand.jain@oracle.com> --- v4: born fs/btrfs/xattr.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)