From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Josh Boyer <jwboyer@redhat.com>
Cc: Steven Rostedt <srostedt@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Perf build failure in v3.4-4842-g61011677
Date: Wed, 23 May 2012 14:13:14 -0300 [thread overview]
Message-ID: <20120523171314.GA1687@infradead.org> (raw)
In-Reply-To: <20120523143304.GF1143@zod.bos.redhat.com>
Em Wed, May 23, 2012 at 10:33:05AM -0400, Josh Boyer escreveu:
> OK, seems Steven fixed the trace-event-python.c file with commit
> aaf045f7233, but missed the perl one. This patch seems to fixup the
> errors.
I reported this to Frédéric, that fixed it, I merged on my perf/core
branch, that Ingo already pulled, thanks anyway,
- Arnaldo
next prev parent reply other threads:[~2012-05-23 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 14:13 Perf build failure in v3.4-4842-g61011677 Josh Boyer
2012-05-23 14:33 ` Josh Boyer
2012-05-23 17:13 ` Arnaldo Carvalho de Melo [this message]
2012-05-23 17:15 ` Josh Boyer
2012-05-23 17:26 ` Arnaldo Carvalho de Melo
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=20120523171314.GA1687@infradead.org \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=jwboyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=srostedt@redhat.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