From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
linux-kernel@vger.kernel.org, Michael Petlan <mpetlan@redhat.com>,
tchen168@asu.edu, Adrian Hunter <adrian.hunter@intel.com>,
Ian Rogers <irogers@google.com>,
James Clark <james.clark@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-perf-users@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: Re: [PATCH v2 1/3] perf tsc: Add missing newlines to debug statements
Date: Mon, 5 Feb 2024 16:18:19 -0800 [thread overview]
Message-ID: <170717858567.1700937.14873687194661225533.b4-ty@kernel.org> (raw)
In-Reply-To: <20240131134940.593788-1-irogers@google.com>
On Wed, 31 Jan 2024 05:49:38 -0800, Ian Rogers wrote:
> It is assumed that debug statements always print a newline, fix two
> missing ones.
>
>
Applied to perf-tools-next, thanks!
[1/3] perf tsc: Add missing newlines to debug statements
commit: 2882358b8b83b417a9d82205ae6aae5be00bd989
[2/3] perf parse-events: Improve error location of terms cloned from an event
commit: f5144ecad74101f87843aa08070df26a3937102a
[3/3] perf parse-events: Print all errors
commit: fd7b8e8fb20f51d60dfee7792806548f3c6a4c2c
Best regards,
--
Namhyung Kim <namhyung@kernel.org>
prev parent reply other threads:[~2024-02-06 0:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 13:49 Ian Rogers
2024-01-31 13:49 ` [PATCH v2 2/3] perf parse-events: Improve error location of terms cloned from an event Ian Rogers
2024-02-01 13:54 ` James Clark
2024-01-31 13:49 ` [PATCH v2 3/3] perf parse-events: Print all errors Ian Rogers
2024-02-01 13:59 ` James Clark
2024-01-31 13:51 ` [PATCH v2 1/3] perf tsc: Add missing newlines to debug statements Ian Rogers
2024-02-06 0:18 ` Namhyung Kim [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=170717858567.1700937.14873687194661225533.b4-ty@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mpetlan@redhat.com \
--cc=peterz@infradead.org \
--cc=tchen168@asu.edu \
/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®