From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 1/2] btrfs-progs: fix the long lines
Date: Mon, 15 Jul 2013 13:35:26 +0800 [thread overview]
Message-ID: <1373866527-10604-2-git-send-email-anand.jain@oracle.com> (raw)
In-Reply-To: <1373866527-10604-1-git-send-email-anand.jain@oracle.com>
trivial: cmds-replace.c contains long lines fix it
Signed-off-by: Anand Jain <anand.jain@oracle.com>
---
cmds-replace.c | 17 ++++++++++-------
1 files changed, 10 insertions(+), 7 deletions(-)
diff --git a/cmds-replace.c b/cmds-replace.c
index 6397bb5..c68986a 100644
--- a/cmds-replace.c
+++ b/cmds-replace.c
@@ -211,8 +211,8 @@ static int cmd_start_replace(int argc, char **argv)
struct btrfs_ioctl_dev_info_args *di_args = NULL;
if (atoi(srcdev) == 0) {
- fprintf(stderr, "Error: Failed to parse the numerical devid value '%s'\n",
- srcdev);
+ fprintf(stderr, "Error: Failed to parse the numerical "\
+ "devid value '%s'\n", srcdev);
goto leave_with_error;
}
start_args.start.srcdevid = (__u64)atoi(srcdev);
@@ -235,8 +235,8 @@ static int cmd_start_replace(int argc, char **argv)
break;
free(di_args);
if (i == fi_args.num_devices) {
- fprintf(stderr, "Error: '%s' is not a valid devid for filesystem '%s'\n",
- srcdev, path);
+ fprintf(stderr, "Error: '%s' is not a valid devid for "\
+ "filesystem '%s'\n", srcdev, path);
goto leave_with_error;
}
} else {
@@ -283,7 +283,8 @@ static int cmd_start_replace(int argc, char **argv)
&total_devs, BTRFS_SUPER_INFO_OFFSET);
if (ret >= 0 && !force_using_targetdev) {
fprintf(stderr,
- "Error, target device %s contains filesystem, use '-f' to force overwriting.\n",
+ "Error, target device %s contains filesystem, "\
+ "use '-f' to force overwriting.\n",
dstdev);
goto leave_with_error;
}
@@ -321,7 +322,8 @@ static int cmd_start_replace(int argc, char **argv)
if (do_not_background) {
if (ret) {
fprintf(stderr,
- "ERROR: ioctl(DEV_REPLACE_START) failed on \"%s\": %s, %s\n",
+ "ERROR: ioctl(DEV_REPLACE_START) failed "\
+ "on \"%s\": %s, %s\n",
path, strerror(errno),
replace_dev_result2string(start_args.result));
goto leave_with_error;
@@ -330,7 +332,8 @@ static int cmd_start_replace(int argc, char **argv)
if (start_args.result !=
BTRFS_IOCTL_DEV_REPLACE_RESULT_NO_ERROR) {
fprintf(stderr,
- "ERROR: ioctl(DEV_REPLACE_START) on \"%s\" returns error: %s\n",
+ "ERROR: ioctl(DEV_REPLACE_START) on \"%s\" "\
+ "returns error: %s\n",
path,
replace_dev_result2string(start_args.result));
goto leave_with_error;
--
1.7.7.6
next prev parent reply other threads:[~2013-07-15 5:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 5:35 [PATCH 0/2] btrfs-progs: misc trivial fixes Anand Jain
2013-07-15 5:35 ` Anand Jain [this message]
2013-07-15 7:25 ` [PATCH 1/2] btrfs-progs: fix the long lines Stefan Behrens
2013-07-15 14:06 ` Eric Sandeen
2013-07-17 2:46 ` Anand Jain
2013-07-15 5:35 ` [PATCH 2/2] btrfs-progs: close_all_devices() declared in multiple files Anand Jain
2013-07-15 8:06 ` Stefan Behrens
2013-07-15 8:40 ` [PATCH] btrfs-progs: close_all_devices() in btrfs-find-root.c does nothing Anand Jain
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=1373866527-10604-2-git-send-email-anand.jain@oracle.com \
--to=anand.jain@oracle.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).