From: mwilck@suse.com
To: Christophe Varoqui <christophe.varoqui@opensvc.com>,
Benjamin Marzinski <bmarzins@redhat.com>
Cc: dm-devel@redhat.com, Martin Wilck <mwilck@suse.com>
Subject: [dm-devel] [PATCH 3/3] kpartx: find_unused_loop_device(): add newlines
Date: Mon, 15 Nov 2021 21:22:01 +0100 [thread overview]
Message-ID: <20211115202201.755-3-mwilck@suse.com> (raw)
In-Reply-To: <20211115202201.755-1-mwilck@suse.com>
From: Martin Wilck <mwilck@suse.com>
... to avoid these messages being joined with the error message
from the caller.
Signed-off-by: Martin Wilck <mwilck@suse.com>
---
kpartx/lopart.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/kpartx/lopart.c b/kpartx/lopart.c
index fccb522..ba9f2c0 100644
--- a/kpartx/lopart.c
+++ b/kpartx/lopart.c
@@ -209,26 +209,26 @@ nothing_found:
}
if (!somedev)
- fprintf(stderr, "mount: could not find any device /dev/loop#");
+ fprintf(stderr, "mount: could not find any device /dev/loop#\n");
else if (!someloop) {
if (loop_known == 1)
fprintf(stderr,
"mount: Could not find any loop device.\n"
- " Maybe /dev/loop# has a wrong major number?");
+ " Maybe /dev/loop# has a wrong major number?\n");
else if (loop_known == -1)
fprintf(stderr,
"mount: Could not find any loop device, and, according to %s,\n"
" this kernel does not know about the loop device.\n"
- " (If so, then recompile or `modprobe loop'.)",
+ " (If so, then recompile or `modprobe loop'.)\n",
PROC_DEVICES);
else
fprintf(stderr,
"mount: Could not find any loop device. Maybe this kernel does not know\n"
" about the loop device (then recompile or `modprobe loop'), or\n"
- " maybe /dev/loop# has the wrong major number?");
+ " maybe /dev/loop# has the wrong major number?\n");
} else
- fprintf(stderr, "mount: could not find any free loop device");
+ fprintf(stderr, "mount: could not find any free loop device\n");
return NULL;
}
--
2.33.1
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2021-11-15 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 20:21 [dm-devel] [PATCH 1/3] kpartx: open /dev/loop-control only once mwilck
2021-11-15 20:22 ` [dm-devel] [PATCH 2/3] kpartx: use opened loop device immediately mwilck
2021-11-16 21:34 ` Martin Wilck
2021-11-15 20:22 ` mwilck [this message]
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=20211115202201.755-3-mwilck@suse.com \
--to=mwilck@suse.com \
--cc=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
/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