From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
"Arjan van de Ven" <arjan@linux.intel.com>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Mike Galbraith" <efault@gmx.de>,
"Paul Mackerras" <paulus@samba.org>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Tom Zanussi" <tzanussi@gmail.com>,
"Yanmin, Zhang" <yanmin_zhang@linux.intel.com>
Subject: Re: [PATCH 0/4] perf tools improvements and minor fixes
Date: Sun, 9 May 2010 21:09:44 -0300 [thread overview]
Message-ID: <20100510000944.GA19192@ghostprotocols.net> (raw)
In-Reply-To: <1273448369-7479-1-git-send-email-acme@infradead.org>
Em Sun, May 09, 2010 at 08:39:25PM -0300, Arnaldo Carvalho de Melo escreveu:
> Hi Ingo,
>
> Please pull from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux-2.6 perf
Oops, retracting the pull request, I found and fixed a bug on the "check
if a struct machine instance was found" patch, v2 coming shortly.
> Arnaldo Carvalho de Melo (4):
> perf symbols: Consider unresolved DSOs in the dso__col_widt calculation
> perf symbols: Check if a struct machine instance was found
> perf session: Embed the host machine data on perf_session
> perf report: Allow limiting the number of entries to print in callchains
prev parent reply other threads:[~2010-05-10 0:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-09 23:39 Arnaldo Carvalho de Melo
2010-05-09 23:39 ` [PATCH 1/4] perf symbols: Consider unresolved DSOs in the dso__col_widt calculation Arnaldo Carvalho de Melo
2010-05-09 23:39 ` [PATCH 2/4] perf symbols: Check if a struct machine instance was found Arnaldo Carvalho de Melo
2010-05-09 23:39 ` [PATCH 3/4] perf session: Embed the host machine data on perf_session Arnaldo Carvalho de Melo
2010-05-09 23:39 ` [PATCH 4/4] perf report: Allow limiting the number of entries to print in callchains Arnaldo Carvalho de Melo
2010-05-10 0:09 ` 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=20100510000944.GA19192@ghostprotocols.net \
--to=acme@infradead.org \
--cc=a.p.zijlstra@chello.nl \
--cc=arjan@linux.intel.com \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=tzanussi@gmail.com \
--cc=yanmin_zhang@linux.intel.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
Powered by JetHome