All of lore.kernel.org
 help / color / mirror / Atom feed
From: damenly.su@gmail.com
To: linux-btrfs@vger.kernel.org
Cc: suy.fnst@cn.fujitsu.com
Subject: [PATCH 1/6] btrfs-progs: adjust arguments of btrfs_lookup_inode_extref()
Date: Wed, 12 Sep 2018 19:20:38 +0000	[thread overview]
Message-ID: <20180912192046.5861-2-suy.fnst@cn.fujitsu.com> (raw)
In-Reply-To: <20180912192046.5861-1-suy.fnst@cn.fujitsu.com>

From: Su Yue <suy.fnst@cn.fujitsu.com>

The argument index is not used in btrfs_lookup_inode_extref(),
so remove it.
And adjust positions its arguments to make it consistent with
kernel part.

No functional change.

Fixes: 260675657767 ("btrfs-progs: Import btrfs_insert/del/lookup_extref() functions.")
Signed-off-by: Su Yue <suy.fnst@cn.fujitsu.com>
---
 ctree.h      | 6 +++---
 inode-item.c | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/ctree.h b/ctree.h
index 4719962df67d..e7f6c5df95f1 100644
--- a/ctree.h
+++ b/ctree.h
@@ -2708,9 +2708,9 @@ int btrfs_lookup_inode(struct btrfs_trans_handle *trans, struct btrfs_root
 		       *root, struct btrfs_path *path,
 		       struct btrfs_key *location, int mod);
 struct btrfs_inode_extref *btrfs_lookup_inode_extref(struct btrfs_trans_handle
-		*trans, struct btrfs_path *path, struct btrfs_root *root,
-		u64 ino, u64 parent_ino, u64 index, const char *name,
-		int namelen, int ins_len);
+		*trans, struct btrfs_root *root, struct btrfs_path *path,
+		const char *name, int namelen, u64 ino, u64 parent_ino,
+		int ins_len);
 int btrfs_del_inode_extref(struct btrfs_trans_handle *trans,
 			   struct btrfs_root *root,
 			   const char *name, int name_len,
diff --git a/inode-item.c b/inode-item.c
index 1cc106670cd4..461557cb83d6 100644
--- a/inode-item.c
+++ b/inode-item.c
@@ -228,9 +228,9 @@ static int btrfs_find_name_in_ext_backref(struct btrfs_path *path,
 }
 
 struct btrfs_inode_extref *btrfs_lookup_inode_extref(struct btrfs_trans_handle
-		*trans, struct btrfs_path *path, struct btrfs_root *root,
-		u64 ino, u64 parent_ino, u64 index, const char *name,
-		int namelen, int ins_len)
+		*trans, struct btrfs_root *root, struct btrfs_path *path,
+		const char *name, int namelen, u64 ino, u64 parent_ino,
+		int ins_len)
 {
 	struct btrfs_key key;
 	struct btrfs_inode_extref *extref;
-- 
2.18.0

  parent reply	other threads:[~2018-09-12 16:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12 19:20 [PATCH 0/6] btrfs-progs: lowmem: bug fixes and inode_extref repair damenly.su
2018-09-12 12:35 ` Su Yue
2018-09-12 19:20 ` damenly.su [this message]
2018-09-12 19:20 ` [PATCH 2/6] btrfs-progs: make btrfs_unlink() lookup inode_extref damenly.su
2018-09-12 19:20 ` [PATCH 3/6] btrfs-progs: lowmem check: find dir_item by di_key in check_dir_item() damenly.su
2018-09-12 19:20 ` [PATCH 4/6] btrfs-progs: lowmem: search key of root again after check_fs_root() under repair damenly.su
2018-09-12 19:20 ` [PATCH 5/6] btrfs-progs: lowmem: continue to check item in last slot while checking inodes damenly.su
2018-09-12 19:20 ` [PATCH 5/7] btrfs-progs: lowmem: improve check_inode_extref() damenly.su
2018-09-12 19:20 ` [PATCH 6/7] btrfs-progs: lowmem: continue to check item in last slot while checking inodes damenly.su
2018-09-12 19:20 ` [PATCH 6/6] btrfs-progs: lowmem: optimization and repair for check_inode_extref() damenly.su
2018-09-12 19:20 ` [PATCH 7/7] btrfs-progs: fsck-tests: add test case inode_extref without dir_item and dir_index damenly.su

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=20180912192046.5861-2-suy.fnst@cn.fujitsu.com \
    --to=damenly.su@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=suy.fnst@cn.fujitsu.com \
    /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.