public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Jens Axboe <jens.axboe@oracle.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH tip 1/3] trace: better manage the context info for events
Date: Tue, 3 Feb 2009 11:29:28 -0200	[thread overview]
Message-ID: <20090203132928.GE17781@ghostprotocols.net> (raw)
In-Reply-To: <20090203132616.GB29046@elte.hu>

Em Tue, Feb 03, 2009 at 02:26:16PM +0100, Ingo Molnar escreveu:
> 
> * Arnaldo Carvalho de Melo <acme@redhat.com> wrote:
> 
> > From: Frederic Weisbecker <fweisbec@gmail.com>
> > 
> > Impact: make trace_event more convenient for tracers
> 
> i've applied your patchset to tip/tracing/bkltrace, thanks guys!
> 
> I see that there might be open questions still but it seems the principle 
> has been agreed upon and the patches were getting larger and harder to test 
> with each daym, so lets do the rest iteratively, ok?

Thanks a lot!

- Arnaldo

      reply	other threads:[~2009-02-03 13:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 22:29 [PATCH tip 1/3] trace: better manage the context info for events Arnaldo Carvalho de Melo
2009-02-03  2:07 ` Frederic Weisbecker
2009-02-03  2:32   ` Steven Rostedt
2009-02-03  9:09     ` Frederic Weisbecker
2009-02-03 12:57       ` Arnaldo Carvalho de Melo
2009-02-03 21:39         ` Frederic Weisbecker
2009-02-03 21:59           ` Arnaldo Carvalho de Melo
2009-02-03 22:02             ` Frederic Weisbecker
2009-02-03 12:54     ` Arnaldo Carvalho de Melo
2009-02-03 13:15     ` Arnaldo Carvalho de Melo
2009-02-03 12:50   ` Arnaldo Carvalho de Melo
2009-02-03 21:31     ` Frederic Weisbecker
2009-02-03 13:26 ` Ingo Molnar
2009-02-03 13:29   ` 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=20090203132928.GE17781@ghostprotocols.net \
    --to=acme@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=jens.axboe@oracle.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