mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Zanussi <tzanussi@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, fweisbec@gmail.com,
	rostedt@goodmis.org, acme@ghostprotocols.net
Subject: Re: [PATCH 0/2] perf trace/scripting: A couple bugfixes
Date: Mon, 07 Dec 2009 01:14:06 -0600	[thread overview]
Message-ID: <1260170046.6632.11.camel@tropicana> (raw)
In-Reply-To: <20091207070556.GB10868@elte.hu>

On Mon, 2009-12-07 at 08:05 +0100, Ingo Molnar wrote:
> * Tom Zanussi <tzanussi@gmail.com> wrote:
> 
> > One fixes a compile error when libperl isn't installed, the other
> > fixes an annoying message about scripting being unsupported even when
> > the perf trace cmd isn't trying to use scripting.
> > 
> > Tom Zanussi (2):
> >   perf trace/scripting: Fix compile err when libperl not installed
> >   perf trace/scripting: Don't display 'scripting unsupported' msg
> >     unnecessarily
> > 
> >  tools/perf/util/trace-event-perl.c |   67 +++++++++++++++++++++++++++++------
> >  tools/perf/util/trace-event-perl.h |    4 ++
> >  2 files changed, 59 insertions(+), 12 deletions(-)
> 
> Applied, thanks a lot Tom!
> 
> ( Note, i already applied patch #1 out of your previous email - this 
>   version has the same content, right? )
> 

Yeah, it's the same.

Thanks,

Tom

> 	Ingo


      reply	other threads:[~2009-12-07  7:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07  5:31 Tom Zanussi
2009-12-07  5:31 ` [PATCH 1/2] perf trace/scripting: Fix compile err when libperl not installed Tom Zanussi
2009-12-07  5:31 ` [PATCH 2/2] perf trace/scripting: Don't display 'scripting unsupported' msg unnecessarily Tom Zanussi
2009-12-07  6:31   ` Wang Liming
2009-12-07  7:13     ` Tom Zanussi
2009-12-07  7:23       ` Wang Liming
2009-12-07  7:10   ` [tip:perf/urgent] " tip-bot for Tom Zanussi
2009-12-07  7:05 ` [PATCH 0/2] perf trace/scripting: A couple bugfixes Ingo Molnar
2009-12-07  7:14   ` Tom Zanussi [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=1260170046.6632.11.camel@tropicana \
    --to=tzanussi@gmail.com \
    --cc=acme@ghostprotocols.net \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®