public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Taeung Song <treeze.taeung@gmail.com>,
	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: Mon, 28 Mar 2016 17:59:56 -0300	[thread overview]
Message-ID: <20160328205956.GE8706@kernel.org> (raw)
In-Reply-To: <20160328195242.GB4687@krava.redhat.com>

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.

  reply	other threads:[~2016-03-28 21:00 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 [this message]
2016-03-28 23:58     ` Taeung Song
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=20160328205956.GE8706@kernel.org \
    --to=acme@kernel.org \
    --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 \
    --cc=treeze.taeung@gmail.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