From: David Miller <davem@davemloft.net>
To: rostedt@goodmis.org
Cc: vapier@gentoo.org, linux-kernel@vger.kernel.org,
fweisbec@gmail.com, mingo@redhat.com,
brueckner@linux.vnet.ibm.com, heiko.carstens@de.ibm.com,
lethal@linux-sh.org
Subject: Re: [PATCH] ftrace: unify arch_syscall_addr() implementations
Date: Fri, 22 Jan 2010 17:36:18 -0800 (PST) [thread overview]
Message-ID: <20100122.173618.90816303.davem@davemloft.net> (raw)
In-Reply-To: <1264170977.31321.382.camel@gandalf.stny.rr.com>
From: Steven Rostedt <rostedt@goodmis.org>
Date: Fri, 22 Jan 2010 09:36:17 -0500
> [ Added Heiko Carstens and Paul Mundt to Cc ]
>
> On Fri, 2010-01-22 at 08:43 -0500, Mike Frysinger wrote:
>> also, does the arch_syscall_addr() even really need to be weak ? or can
>> we assume that everyone is going to be sane and do it the same way ...
>>
>> Documentation/trace/ftrace-design.txt | 6 +++++-
>> arch/s390/kernel/ftrace.c | 10 ----------
>> arch/sh/kernel/ftrace.c | 9 ---------
>> arch/sparc/kernel/ftrace.c | 11 -----------
>> arch/x86/kernel/ftrace.c | 10 ----------
>> include/linux/ftrace.h | 6 ++++++
>> kernel/trace/trace_syscalls.c | 6 +++++
>
> Actually for this patch to be accepted, we need to get the acks from the
> maintainers of s390, sh, and sparc since it touches their code. Doesn't
> matter if it is just removing duplicate code. Still need their acks.
Acked-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2010-01-23 1:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 13:43 Mike Frysinger
2010-01-22 14:36 ` Steven Rostedt
2010-01-22 16:37 ` Heiko Carstens
2010-01-22 19:32 ` Mike Frysinger
2010-01-23 1:38 ` David Miller
2010-01-23 1:36 ` David Miller [this message]
2010-01-26 3:03 ` Paul Mundt
2010-01-27 4:50 ` Mike Frysinger
2010-01-23 7:10 ` [PATCH v2] " Mike Frysinger
2010-01-23 8:28 ` David Miller
2010-01-23 19:13 ` Mike Frysinger
2010-01-26 9:40 ` [PATCH v3] " Mike Frysinger
2010-01-26 11:29 ` Heiko Carstens
2010-02-03 22:48 ` Frederic Weisbecker
2010-02-27 12:51 ` [tip:tracing/core] tracing: Unify " tip-bot for Mike Frysinger
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=20100122.173618.90816303.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brueckner@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=vapier@gentoo.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
Powered by JetHome