From: Taeung Song <treeze.taeung@gmail.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Jiri Olsa <jolsa@redhat.com>
Cc: linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 1/3] perf config: Remove duplicated the code calling set_buildid_dir
Date: Tue, 29 Mar 2016 08:58:20 +0900 [thread overview]
Message-ID: <56F9C51C.5050406@gmail.com> (raw)
In-Reply-To: <20160328205956.GE8706@kernel.org>
Hi, jirka and Arnaldo
On 03/29/2016 05:59 AM, Arnaldo Carvalho de Melo wrote:
> Em Mon, Mar 28, 2016 at 09:52:42PM +0200, Jiri Olsa escreveu:
>> On Mon, Mar 28, 2016 at 02:22:18AM +0900, Taeung Song wrote:
>>> Cc: Jiri Olsa <jolsa@kernel.org>
>>> Cc: Namhyung Kim <namhyung@kernel.org>
>>> Signed-off-by: Taeung Song <treeze.taeung@gmail.com>
>>
>> for the patchset:
>>
>> Acked-by: Jiri Olsa <jolsa@kernel.org>
>
> Thanks, applied.
Thank you !! :-)
Taeung
next prev parent reply other threads:[~2016-03-28 23:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 17:22 [PATCH 1/3] perf config: Remove duplicated the code calling set_buildid_dir Taeung Song
2016-03-27 17:22 ` [PATCH 2/3] perf config: Rework buildid_dir_command_config to perf_buildid_config Taeung Song
2016-03-31 6:53 ` [tip:perf/core] " tip-bot for Taeung Song
2016-03-27 17:22 ` [PATCH 3/3] perf config: Rename 'v' to 'home' at set_buildid_dir Taeung Song
2016-03-31 6:54 ` [tip:perf/core] perf config: Rename 'v' to 'home' in set_buildid_dir() tip-bot for Taeung Song
2016-03-28 19:52 ` [PATCH 1/3] perf config: Remove duplicated the code calling set_buildid_dir Jiri Olsa
2016-03-28 20:59 ` Arnaldo Carvalho de Melo
2016-03-28 23:58 ` Taeung Song [this message]
2016-03-31 6:53 ` [tip:perf/core] perf config: Remove duplicated set_buildid_dir calls tip-bot for Taeung Song
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=56F9C51C.5050406@gmail.com \
--to=treeze.taeung@gmail.com \
--cc=arnaldo.melo@gmail.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/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