public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Li Zefan <lizf@cn.fujitsu.com>,
	Masami Hiramatsu <mhiramat@redhat.com>,
	Jason Baron <jbaron@redhat.com>,
	Lai Jiangshan <laijs@cn.fujitsu.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Paul Mundt <lethal@linux-sh.org>
Subject: Re: [GIT PULL v2] tracing/syscalls: Arch code shrinks, easier arch integration
Date: Wed, 14 Oct 2009 00:25:08 +0200	[thread overview]
Message-ID: <20091013222506.GA4952@nowhere> (raw)
In-Reply-To: <1253351338-5301-1-git-send-email-fweisbec@gmail.com>

On Sat, Sep 19, 2009 at 11:08:56AM +0200, Frederic Weisbecker wrote:
> Ingo, Heiko,
> 
> I've updated the patches following your reviews.
> Please tell me if you see another troubles.
> 
> The new tree can be pulled from:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
> 	tracing/syscalls-v2
> 
> Thanks,
> 	Frederic.


Ingo,

I wonder if you have forgotten this pull request, or if there is a
problem with it.

It's still cleanly mergeable into tip:/tracing/core.

Thanks.



 
> Frederic Weisbecker (2):
>       tracing: Move syscalls metadata handling from arch to core
>       tracing: Document HAVE_SYSCALL_TRACEPOINTS needs
> 
>  Documentation/trace/ftrace-design.txt |   13 ++++-
>  arch/s390/kernel/ftrace.c             |   67 +-------------------------
>  arch/x86/kernel/ftrace.c              |   76 +----------------------------
>  include/trace/syscall.h               |    2 +-
>  kernel/trace/trace_syscalls.c         |   86 +++++++++++++++++++++++++++++++++
>  5 files changed, 102 insertions(+), 142 deletions(-)


  reply	other threads:[~2009-10-13 22:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-19  5:39 [GIT PULL] tracing/syscalls: Arch code shrinks, easier arch integration Frederic Weisbecker
2009-09-19  5:39 ` [PATCH 1/2] tracing: Move syscalls metadata handling from arch to core Frederic Weisbecker
2009-09-19  7:16   ` Ingo Molnar
2009-09-19  7:48   ` Heiko Carstens
2009-09-19  8:12     ` Frederic Weisbecker
2009-09-19  5:39 ` [PATCH 2/2] tracing: Document HAVE_FTRACE_SYSCALLS needs Frederic Weisbecker
2009-09-19  7:17   ` Ingo Molnar
2009-09-19  7:22     ` Frederic Weisbecker
2009-09-19  7:28       ` Ingo Molnar
2009-09-19  7:29         ` Frederic Weisbecker
2009-09-19  9:08 ` [GIT PULL v2] tracing/syscalls: Arch code shrinks, easier arch integration Frederic Weisbecker
2009-10-13 22:25   ` Frederic Weisbecker [this message]
2009-10-14  6:18     ` Ingo Molnar
2009-10-14  7:28       ` Heiko Carstens
2009-09-19  9:08 ` [PATCH 1/2 v2] tracing: Move syscalls metadata handling from arch to core Frederic Weisbecker
2009-09-19  9:08 ` [PATCH 2/2 v2] tracing: Document HAVE_SYSCALL_TRACEPOINTS needs Frederic Weisbecker

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=20091013222506.GA4952@nowhere \
    --to=fweisbec@gmail.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=jbaron@redhat.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mhiramat@redhat.com \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=schwidefsky@de.ibm.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