linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v4 04/10] btrfs: rename fs_info argument to fs_private
Date: Sat, 23 Feb 2019 01:39:46 +0800	[thread overview]
Message-ID: <1550857192-10513-5-git-send-email-anand.jain@oracle.com> (raw)
In-Reply-To: <1550857192-10513-1-git-send-email-anand.jain@oracle.com>

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(-)

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;
-- 
1.8.3.1


  parent reply	other threads:[~2019-02-22 17:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22 17:39 [PATCH v4 00/10] Misc props.c cleanups Anand Jain
2019-02-22 17:39 ` [PATCH v4 01/10] btrfs: kill __btrfs_set_prop() Anand Jain
2019-02-22 17:39 ` [PATCH v4 02/10] btrfs: drop redundant forward declaration in props.c Anand Jain
2019-02-22 17:39 ` [PATCH v4 03/10] btrfs: trivial, fix c coding style Anand Jain
2019-02-27 16:05   ` David Sterba
2019-02-28  9:50     ` Anand Jain
2019-02-22 17:39 ` Anand Jain [this message]
2019-02-27 16:10   ` [PATCH v4 04/10] btrfs: rename fs_info argument to fs_private David Sterba
2019-02-22 17:39 ` [PATCH v4 05/10] btrfs: refactor btrfs_set_prop add btrfs_set_prop_trans Anand Jain
2019-02-22 17:39 ` [PATCH v4 06/10] btrfs: start transaction in btrfs_set_prop_trans Anand Jain
2019-02-27 16:08   ` David Sterba
2019-02-28 10:36     ` Anand Jain
2019-02-28 16:00       ` David Sterba
2019-02-22 17:39 ` [PATCH v4 07/10] btrfs: start transaction in btrfs_set_acl Anand Jain
2019-02-22 17:39 ` [PATCH v4 08/10] btrfs: start transaction in btrfs_xattr_handler_set Anand Jain
2019-02-22 17:39 ` [PATCH v4 09/10] btrfs: btrfs_setxattr argument trans is never NULL Anand Jain
2019-02-27 16:16   ` David Sterba
2019-02-28 10:40     ` Anand Jain
2019-02-22 17:39 ` [PATCH v4 10/10] btrfs: kill btrfs_setxattr Anand Jain
2019-02-27 16:21   ` David Sterba
2019-02-28 11:10     ` Anand Jain

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=1550857192-10513-5-git-send-email-anand.jain@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).