public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "Matthias Maennich via libabigail" <libabigail@sourceware.org>
To: libabigail@sourceware.org
Cc: dodji@seketeli.org, kernel-team@android.com, maennich@google.com
Subject: [PATCH v2] kmidiff: fix help message
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <20191004152631.251414-1-maennich@google.com> (raw)
In-Reply-To: <20191004130021.166473-1-maennich@google.com>

Add the missing line breaks.

	* tools/kmidiff.c (display_usage): add missing line breaks to
	help text

Signed-off-by: Matthias Maennich <maennich@google.com>
---
 tools/kmidiff.cc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tools/kmidiff.cc b/tools/kmidiff.cc
index 4afc201e7afd..842381f8917e 100644
--- a/tools/kmidiff.cc
+++ b/tools/kmidiff.cc
@@ -115,9 +115,9 @@ display_usage(const string& prog_name, ostream& out)
     << " --version|-v  display program version information and exit\n"
     << " --verbose  display verbose messages\n"
     << " --debug-info-dir1|--d1 <path> the root for the debug info of "
-    "the first kernel"
+	"the first kernel\n"
     << " --debug-info-dir2|--d2 <path> the root for the debug info of "
-    "the second kernel"
+	"the second kernel\n"
     << " --vmlinux1|--l1 <path>  the path to the first vmlinux\n"
     << " --vmlinux2|--l2 <path>  the path to the second vmlinux\n"
     << " --suppressions|--suppr <path>  specify a suppression file\n"
-- 
2.23.0.581.g78d2f28ef7-goog

  reply	other threads:[~2019-10-04 15:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01  0:00 [PATCH] " Matthias Maennich via libabigail
2019-01-01  0:00 ` Matthias Maennich via libabigail [this message]
2019-01-01  0:00   ` [PATCH v2] " Dodji Seketeli

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=20191004152631.251414-1-maennich@google.com \
    --to=libabigail@sourceware.org \
    --cc=dodji@seketeli.org \
    --cc=kernel-team@android.com \
    --cc=maennich@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).