linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	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,
	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:10:36 +0200	[thread overview]
Message-ID: <20090401111036.GA5894@pengutronix.de> (raw)
In-Reply-To: <20090401110512.GB15442@elte.hu>

Hello Ingo,

On Wed, Apr 01, 2009 at 01:05:12PM +0200, Ingo Molnar wrote:
> 
> * 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.
I'm not sure that they really conflict.  My change ("tracing: make
CALLER_ADDRx overwriteable") only created the empty include file that I
can unconditionally include <asm/ftrace.h>.

But I don't know for sure.

Best regards
Uwe

-- 
Pengutronix e.K.                              | Uwe Kleine-König            |
Industrial Linux Solutions                    | http://www.pengutronix.de/  |

  reply	other threads:[~2009-04-01 11:11 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
2009-04-01 11:10   ` Uwe Kleine-König [this message]
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=20090401111036.GA5894@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=deller@gmx.de \
    --cc=hpa@zytor.com \
    --cc=kyle@mcmartin.ca \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sfr@canb.auug.org.au \
    --cc=srostedt@redhat.com \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).