From: Ingo Molnar <mingo@elte.hu>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: linux-kernel@vger.kernel.org, 2nddept-manager@sdl.hitachi.co.jp,
Frederic Weisbecker <fweisbec@gmail.com>,
Lin Ming <ming.m.lin@intel.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [GIT PULL 0/5] perf/urgent fixes
Date: Wed, 6 Apr 2011 13:10:54 +0200 [thread overview]
Message-ID: <20110406111054.GA24706@elte.hu> (raw)
In-Reply-To: <1302087623-14724-1-git-send-email-acme@infradead.org>
* Arnaldo Carvalho de Melo <acme@infradead.org> wrote:
> Hi Ingo,
>
> Please consider pulling from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux-2.6 perf/urgent
>
> Regards,
>
> - Arnaldo
>
>
> Masami Hiramatsu (5):
> perf probe: Fix to ensure function declared file
> perf probe: Fix to remove redundant close
> perf probe: Fix multiple --vars options behavior
> perf probe: Fix to find recursively inlined function
> perf probe: Fix listing incorrect line number with inline function
>
> tools/perf/util/probe-event.c | 19 ++---
> tools/perf/util/probe-finder.c | 159 ++++++++++++++++++++++++++--------------
> 2 files changed, 113 insertions(+), 65 deletions(-)
Pulled, thanks a lot Arnaldo!
Ingo
next prev parent reply other threads:[~2011-04-06 11:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 11:00 Arnaldo Carvalho de Melo
2011-04-06 11:00 ` [PATCH 1/5] perf probe: Fix to ensure function declared file Arnaldo Carvalho de Melo
2011-04-06 11:00 ` [PATCH 2/5] perf probe: Fix to remove redundant close Arnaldo Carvalho de Melo
2011-04-06 11:00 ` [PATCH 3/5] perf probe: Fix multiple --vars options behavior Arnaldo Carvalho de Melo
2011-04-06 11:00 ` [PATCH 4/5] perf probe: Fix to find recursively inlined function Arnaldo Carvalho de Melo
2011-04-06 11:00 ` [PATCH 5/5] perf probe: Fix listing incorrect line number with inline function Arnaldo Carvalho de Melo
2011-04-06 11:10 ` Ingo Molnar [this message]
2011-05-27 21:45 [GIT PULL 0/5] perf/urgent fixes Arnaldo Carvalho de Melo
2011-05-28 9:41 ` Ingo Molnar
2011-05-29 14:12 ` Arnaldo Carvalho de Melo
2011-05-29 14:30 ` Ingo Molnar
2012-04-05 23:28 Arnaldo Carvalho de Melo
2012-04-14 17:03 Arnaldo Carvalho de Melo
2012-04-15 6:04 ` Ingo Molnar
2013-09-10 18:11 Arnaldo Carvalho de Melo
2013-09-11 5:46 ` Ingo Molnar
2013-09-11 5:55 ` Ingo Molnar
2013-09-11 14:08 ` Arnaldo Carvalho de Melo
2013-09-12 5:45 ` Ingo Molnar
2013-12-02 6:58 ` Brian Gitonga Marete
2013-11-19 20:41 Arnaldo Carvalho de Melo
2013-11-20 13:32 ` Ingo Molnar
2014-02-13 21:15 Arnaldo Carvalho de Melo
2014-02-22 16:23 ` Ingo Molnar
2015-09-17 18:54 Arnaldo Carvalho de Melo
2015-09-18 5:46 ` Ingo Molnar
2015-11-11 21:56 Arnaldo Carvalho de Melo
2015-11-12 6:38 ` Ingo Molnar
2015-11-13 20:57 Arnaldo Carvalho de Melo
2015-11-18 5:57 ` Ingo Molnar
2015-12-07 20:06 Arnaldo Carvalho de Melo
2015-12-08 5:09 ` Ingo Molnar
2017-12-18 14:39 Arnaldo Carvalho de Melo
2017-12-18 17:11 ` Ingo Molnar
2018-05-14 12:23 Arnaldo Carvalho de Melo
2018-05-15 6:21 ` Ingo Molnar
2018-07-30 20:50 Arnaldo Carvalho de Melo
2018-07-31 5:51 ` Ingo Molnar
2018-10-05 16:10 Arnaldo Carvalho de Melo
2018-10-05 16:14 ` Ingo Molnar
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=20110406111054.GA24706@elte.hu \
--to=mingo@elte.hu \
--cc=2nddept-manager@sdl.hitachi.co.jp \
--cc=acme@ghostprotocols.net \
--cc=acme@infradead.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=ming.m.lin@intel.com \
--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
Powered by JetHome