From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
David Ahern <dsahern@gmail.com>, Thomas Renninger <trenn@suse.de>
Subject: Re: [PATCHv2 0/5] perf tools: Remove event types data
Date: Mon, 15 Jul 2013 16:33:48 -0300 [thread overview]
Message-ID: <20130715193348.GB3298@ghostprotocols.net> (raw)
In-Reply-To: <87txk0w44w.fsf@sejong.aot.lge.com>
Em Fri, Jul 12, 2013 at 05:53:35PM +0900, Namhyung Kim escreveu:
> For the whole patchset:
>
> Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks, applied.
- Arnaldo
prev parent reply other threads:[~2013-07-15 19:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 15:28 [PATCHv2 0/5] perf tools: Remove event types data Jiri Olsa
2013-07-11 15:28 ` [PATCH 1/5] perf tools: Add traceevent lib event-parse.h include to timechart Jiri Olsa
2013-07-19 7:52 ` [tip:perf/core] perf timechart: Use traceevent lib event-parse.h include tip-bot for Jiri Olsa
2013-07-11 15:28 ` [PATCH 2/5] perf tools: Remove event types framework only user Jiri Olsa
2013-07-19 7:53 ` [tip:perf/core] perf timechart: " tip-bot for Jiri Olsa
2013-07-11 15:28 ` [PATCH 3/5] perf tools: Remove event types from perf data file Jiri Olsa
2013-07-19 7:53 ` [tip:perf/core] " tip-bot for Jiri Olsa
2013-07-11 15:28 ` [PATCH 4/5] perf tools: Remove event types pushing from record command Jiri Olsa
2013-07-19 7:53 ` [tip:perf/core] perf record: Remove event types pushing tip-bot for Jiri Olsa
2013-07-11 15:28 ` [PATCH 5/5] perf tools: Remove event types framework completely Jiri Olsa
2013-07-19 7:53 ` [tip:perf/core] " tip-bot for Jiri Olsa
2013-07-12 8:53 ` [PATCHv2 0/5] perf tools: Remove event types data Namhyung Kim
2013-07-15 19:33 ` Arnaldo Carvalho de Melo [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=20130715193348.GB3298@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=trenn@suse.de \
/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