From: Frederic Weisbecker <fweisbec@gmail.com>
To: Aristeu Rozanski <aris@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Steven Rostedt <rostedt@goodmis.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ftrace: build ftrace.o when CONFIG_FTRACE_SYSCALLS is set for s390
Date: Thu, 19 Nov 2009 04:03:03 +0100 [thread overview]
Message-ID: <20091119030302.GB4970@nowhere> (raw)
In-Reply-To: <20091118204044.GR3441@redhat.com>
On Wed, Nov 18, 2009 at 03:40:44PM -0500, Aristeu Rozanski wrote:
> Trying to build a s390x kernel with CONFIG_FTRACE_SYSCALLS will fail
> because ftrace.o is not built/linked.
>
> Signed-off-by: Aristeu Rozanski <aris@redhat.com>
>
> ---
> arch/s390/kernel/Makefile | 1 +
> 1 file changed, 1 insertion(+)
>
> --- linus-2.6.orig/arch/s390/kernel/Makefile 2009-10-30 17:49:10.000000000 -0400
> +++ linus-2.6/arch/s390/kernel/Makefile 2009-11-18 15:39:52.000000000 -0500
> @@ -44,6 +44,7 @@ obj-$(CONFIG_KPROBES) += kprobes.o
> obj-$(CONFIG_FUNCTION_TRACER) += $(if $(CONFIG_64BIT),mcount64.o,mcount.o)
> obj-$(CONFIG_DYNAMIC_FTRACE) += ftrace.o
> obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o
> +obj-$(CONFIG_FTRACE_SYSCALLS) += ftrace.o
>
> # Kexec part
> S390_KEXEC_OBJS := machine_kexec.o crash.o
>
Thanks!
Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
We probably want this patch for .32
Not sure in which tree it best fits though, -tip or s390?
(Adding more people in Cc).
next prev parent reply other threads:[~2009-11-19 3:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 20:40 [PATCH] ftrace: build ftrace.o when CONFIG_FTRACE_SYSCALLS is set for s390 Aristeu Rozanski
2009-11-19 3:03 ` Frederic Weisbecker [this message]
2009-11-19 3:24 ` Ingo Molnar
2009-11-19 11:44 ` Martin Schwidefsky
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=20091119030302.GB4970@nowhere \
--to=fweisbec@gmail.com \
--cc=aris@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.