From: Gu Jinxiang <gujx@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Subject: [PATCH] btrfs-progs: remove BTRFS_LIST_LAYOUT_RAW
Date: Tue, 15 May 2018 17:17:14 +0800 [thread overview]
Message-ID: <1526375834-28486-1-git-send-email-gujx@cn.fujitsu.com> (raw)
Since
commit 9005b603d723 ("btrfs-progs: use libbtrfsutil for subvol show"),
BTRFS_LIST_LAYOUT_RAW has no usage.
So, remove it.
Signed-off-by: Gu Jinxiang <gujx@cn.fujitsu.com>
---
btrfs-list.c | 20 --------------------
btrfs-list.h | 3 +--
2 files changed, 1 insertion(+), 22 deletions(-)
diff --git a/btrfs-list.c b/btrfs-list.c
index e01c5899..16be6b2f 100644
--- a/btrfs-list.c
+++ b/btrfs-list.c
@@ -1374,23 +1374,6 @@ static void print_subvolume_column(struct root_info *subv,
}
}
-static void print_one_subvol_info_raw(struct root_info *subv,
- const char *raw_prefix)
-{
- int i;
-
- for (i = 0; i < BTRFS_LIST_ALL; i++) {
- if (!btrfs_list_columns[i].need_print)
- continue;
-
- if (raw_prefix)
- printf("%s",raw_prefix);
-
- print_subvolume_column(subv, i);
- }
- printf("\n");
-}
-
static void print_one_subvol_info_table(struct root_info *subv)
{
int i;
@@ -1480,9 +1463,6 @@ static void print_all_subvol_info(struct root_lookup *sorted_tree,
case BTRFS_LIST_LAYOUT_TABLE:
print_one_subvol_info_table(entry);
break;
- case BTRFS_LIST_LAYOUT_RAW:
- print_one_subvol_info_raw(entry, raw_prefix);
- break;
}
next:
n = rb_next(n);
diff --git a/btrfs-list.h b/btrfs-list.h
index 6e5fc778..299e3122 100644
--- a/btrfs-list.h
+++ b/btrfs-list.h
@@ -33,8 +33,7 @@
enum btrfs_list_layout {
BTRFS_LIST_LAYOUT_DEFAULT = 0,
- BTRFS_LIST_LAYOUT_TABLE,
- BTRFS_LIST_LAYOUT_RAW
+ BTRFS_LIST_LAYOUT_TABLE
};
/*
--
2.17.0
next reply other threads:[~2018-05-15 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 9:17 Gu Jinxiang [this message]
2018-05-16 8:11 ` [PATCH] btrfs-progs: remove BTRFS_LIST_LAYOUT_RAW Nikolay Borisov
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=1526375834-28486-1-git-send-email-gujx@cn.fujitsu.com \
--to=gujx@cn.fujitsu.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).