From: David Sterba <dsterba@suse.cz>
To: linux-btrfs@vger.kernel.org
Cc: chris.mason@fusionio.com, David Sterba <dsterba@suse.cz>
Subject: [PATCH] btrfs-progs: sort devices by id in fi show
Date: Tue, 17 Jul 2012 12:51:59 +0200 [thread overview]
Message-ID: <1342522319-26017-1-git-send-email-dsterba@suse.cz> (raw)
Devids are printed in descending order now, switch it to ascending.
Signed-off-by: David Sterba <dsterba@suse.cz>
---
btrfs-show.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/btrfs-show.c b/btrfs-show.c
index 8210fd2..2a85932 100644
--- a/btrfs-show.c
+++ b/btrfs-show.c
@@ -77,7 +77,7 @@ static void print_one_uuid(struct btrfs_fs_devices *fs_devices)
free(super_bytes_used);
- list_for_each(cur, &fs_devices->devices) {
+ list_for_each_prev(cur, &fs_devices->devices) {
char *total_bytes;
char *bytes_used;
device = list_entry(cur, struct btrfs_device, dev_list);
--
1.7.6.233.gd79bc
reply other threads:[~2012-07-17 10:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1342522319-26017-1-git-send-email-dsterba@suse.cz \
--to=dsterba@suse.cz \
--cc=chris.mason@fusionio.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).