From: Ingo Molnar <mingo@elte•hu>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix•de>,
"H. Peter Anvin" <hpa@zytor•com>,
linux-next@vger•kernel.org, Helge Deller <deller@gmx•de>,
Kyle McMartin <kyle@mcmartin•ca>,
linux-parisc@vger•kernel.org,
Uwe Kleine-Koenig <u.kleine-koenig@pengutronix•de>,
Steven Rostedt <srostedt@redhat•com>
Subject: Re: linux-next: manual merge of the tracing tree with the parisc tree
Date: Wed, 1 Apr 2009 13:05:12 +0200 [thread overview]
Message-ID: <20090401110512.GB15442@elte.hu> (raw)
In-Reply-To: <20090401113740.7f425e02.sfr@canb.auug.org.au>
* Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> Hi all,
>
> Today's linux-next merge of the tracing tree got a conflict in
> arch/parisc/include/asm/ftrace.h between commit
> d75f054a2cf0614ff63d534ff21ca8eaab41e713 ("parisc: add ftrace (function
> and graph tracer) functionality") from the parisc tree and commit
> c79a61f55773d2519fd0525bf58385f7d20752d3 ("tracing: make CALLER_ADDRx
> overwriteable") from the tracing tree.
>
> The former adds a non-trivial version of the file, so I used that.
You need to be careful, the two trees likely cannot be combined like
that, ftrace will likely stop working on parisc because you combine
old-parisc with new-ftrace.
If the two trees are integrated without forward-porting the parisc
ftrace port to the new facilities, then it's safer to do a trivial
patch that disables the ftrace bits on parisc.
Ingo
next prev parent reply other threads:[~2009-04-01 11:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 0:37 linux-next: manual merge of the tracing tree with the parisc tree Stephen Rothwell
2009-04-01 6:54 ` Uwe Kleine-König
2009-04-01 11:05 ` Ingo Molnar [this message]
2009-04-01 11:10 ` Uwe Kleine-König
2009-04-01 11:19 ` Ingo Molnar
2009-04-01 17:50 ` Kyle McMartin
2009-04-02 11:32 ` Stephen Rothwell
2009-04-02 13:54 ` James Bottomley
2009-04-02 15:22 ` Kyle McMartin
2009-04-03 14:15 ` Ingo Molnar
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=20090401110512.GB15442@elte.hu \
--to=mingo@elte$(echo .)hu \
--cc=deller@gmx$(echo .)de \
--cc=hpa@zytor$(echo .)com \
--cc=kyle@mcmartin$(echo .)ca \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-parisc@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=srostedt@redhat$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
--cc=u.kleine-koenig@pengutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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