From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Aristeu Rozanski <aris@redhat.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-kernel@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH] ftrace: build ftrace.o when CONFIG_FTRACE_SYSCALLS is set for s390
Date: Thu, 19 Nov 2009 12:44:15 +0100 [thread overview]
Message-ID: <20091119124415.0fd92f4d@mschwide.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20091119032439.GB13378@elte.hu>
On Thu, 19 Nov 2009 04:24:39 +0100
Ingo Molnar <mingo@elte.hu> wrote:
>
> * Aristeu Rozanski <aris@redhat.com> 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
>
> Nice catch. AFAICS the build failure should trigger if DYNAMIC_FTRACE
> and FUNCTION_GRAPH_TRACER is disabled - and i think it affects current
> mainline too.
>
> I've Cc:-ed Martin and Heiko - i think this fix is for the s390 tree.
Yes, I will add that to the s390 tree for the next merge window.
Thanks.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
prev parent reply other threads:[~2009-11-19 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 20:40 Aristeu Rozanski
2009-11-19 3:03 ` Frederic Weisbecker
2009-11-19 3:24 ` Ingo Molnar
2009-11-19 11:44 ` Martin Schwidefsky [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=20091119124415.0fd92f4d@mschwide.boeblingen.de.ibm.com \
--to=schwidefsky@de.ibm.com \
--cc=aris@redhat.com \
--cc=fweisbec@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®