From: He Kuang <hekuang@huawei.com>
To: <peterz@infradead.org>, <will.deacon@arm.com>, <mingo@redhat.com>,
<acme@kernel.org>, <alexander.shishkin@linux.intel.com>,
<mhiramat@kernel.org>, <jolsa@redhat.com>, <hekuang@huawei.com>
Cc: <wangnan0@huawei.com>, <bintian.wang@huawei.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v4 2/2] perf tools: Add missing newline in debug messages
Date: Tue, 7 Feb 2017 07:34:12 +0000 [thread overview]
Message-ID: <20170207073412.26983-2-hekuang@huawei.com> (raw)
In-Reply-To: <20170207073412.26983-1-hekuang@huawei.com>
These two debug messages are missing the trailing newline.
Signed-off-by: He Kuang <hekuang@huawei.com>
---
tools/perf/util/bpf-loader.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/perf/util/bpf-loader.c b/tools/perf/util/bpf-loader.c
index 36c8611..bc6bc70 100644
--- a/tools/perf/util/bpf-loader.c
+++ b/tools/perf/util/bpf-loader.c
@@ -670,13 +670,13 @@ int bpf__probe(struct bpf_object *obj)
err = convert_perf_probe_events(pev, 1);
if (err < 0) {
- pr_debug("bpf_probe: failed to convert perf probe events");
+ pr_debug("bpf_probe: failed to convert perf probe events\n");
goto out;
}
err = apply_perf_probe_events(pev, 1);
if (err < 0) {
- pr_debug("bpf_probe: failed to apply perf probe events");
+ pr_debug("bpf_probe: failed to apply perf probe events\n");
goto out;
}
--
1.8.5.2
next prev parent reply other threads:[~2017-02-07 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 7:34 [PATCH v4 1/2] perf tools arm64: Add support for generating bpf prologue He Kuang
2017-02-07 7:34 ` He Kuang [this message]
2017-02-07 12:12 ` Will Deacon
2017-02-07 15:02 ` Arnaldo Carvalho de Melo
2017-02-07 13:43 ` Masami Hiramatsu
2017-02-10 7:40 ` [tip:perf/core] " tip-bot for He Kuang
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=20170207073412.26983-2-hekuang@huawei.com \
--to=hekuang@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bintian.wang@huawei.com \
--cc=jolsa@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=wangnan0@huawei.com \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®