From: jeffm@suse.com
To: linux-btrfs@vger.kernel.org
Cc: Jeff Mahoney <jeffm@suse.com>
Subject: [PATCH 2/3] btrfs-progs: convert: add missing newlines for printfs
Date: Tue, 25 Jul 2017 16:54:42 -0400 [thread overview]
Message-ID: <20170725205443.29874-2-jeffm@suse.com> (raw)
In-Reply-To: <20170725205443.29874-1-jeffm@suse.com>
From: Jeff Mahoney <jeffm@suse.com>
There are two printfs with missing newlines that end up making the
output wonky.
Signed-off-by: Jeff Mahoney <jeffm@suse.com>
---
convert/main.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/convert/main.c b/convert/main.c
index c56382e..01657a6 100644
--- a/convert/main.c
+++ b/convert/main.c
@@ -1285,7 +1285,7 @@ static int do_convert(const char *devname, u32 convert_flags, u32 nodesize,
goto fail;
}
- printf("creating btrfs metadata");
+ printf("creating btrfs metadata\n");
ctx.max_copy_inodes = (cctx.inodes_count - cctx.free_inodes_count);
ctx.cur_copy_inodes = 0;
@@ -1348,7 +1348,7 @@ static int do_convert(const char *devname, u32 convert_flags, u32 nodesize,
close_ctree(root);
close(fd);
- printf("conversion complete");
+ printf("conversion complete\n");
return 0;
fail:
clean_convert_context(&cctx);
--
2.11.0
next prev parent reply other threads:[~2017-07-25 20:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 20:54 [PATCH 1/3] btrfs-progs: convert: properly handle reserved ranges while iterating files jeffm
2017-07-25 20:54 ` jeffm [this message]
2017-07-25 20:54 ` [PATCH 3/3] btrfs-progs: convert: add support for converting reiserfs jeffm
2017-07-25 20:57 ` Jeff Mahoney
2017-08-22 17:09 ` David Sterba
2017-07-27 1:35 ` [PATCH 1/3] btrfs-progs: convert: properly handle reserved ranges while iterating files Qu Wenruo
2017-07-27 16:38 ` Jeff Mahoney
2017-07-27 21:29 ` Jeff Mahoney
2017-07-28 1:12 ` Qu Wenruo
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=20170725205443.29874-2-jeffm@suse.com \
--to=jeffm@suse.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).