From: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Cc: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
Subject: [PATCH 3/3] btrfs-progs: remove meaningless debug info for restore
Date: Thu, 28 Aug 2014 10:25:55 +0800 [thread overview]
Message-ID: <1409192755-1826-3-git-send-email-guihc.fnst@cn.fujitsu.com> (raw)
In-Reply-To: <1409192755-1826-1-git-send-email-guihc.fnst@cn.fujitsu.com>
The printf of @offset enlightens the user little.
And the restore cmd is not a debugging tool, so just
remove the debug-info-like printf.
Signed-off-by: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
---
cmds-restore.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/cmds-restore.c b/cmds-restore.c
index 918f1fb..648fbc9 100644
--- a/cmds-restore.c
+++ b/cmds-restore.c
@@ -310,8 +310,6 @@ static int copy_one_extent(struct btrfs_root *root, int fd,
if (compress == BTRFS_COMPRESS_NONE)
bytenr += offset;
- if (offset)
- printf("offset is %Lu\n", offset);
/* we found a hole */
if (disk_size == 0)
return 0;
--
1.8.1.4
next prev parent reply other threads:[~2014-08-28 2:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 2:25 [PATCH 1/3] btrfs-progs: fix len of read_extent_buffer for inline extent in restore Gui Hecheng
2014-08-28 2:25 ` [PATCH 2/3] btrfs-progs: fix next_leaf in restore as it improperly skips some slots Gui Hecheng
2014-08-28 2:25 ` Gui Hecheng [this message]
2014-08-29 14:49 ` [PATCH 3/3] btrfs-progs: remove meaningless debug info for restore David Sterba
2014-09-01 1:35 ` Gui Hecheng
2014-09-01 1:47 ` [PATCH] btrfs-progs: move debug info to verbose mode " Gui Hecheng
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=1409192755-1826-3-git-send-email-guihc.fnst@cn.fujitsu.com \
--to=guihc.fnst@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).