Return-Path: Received: from mx2.mail.elte.hu (mx2.mail.elte.hu [157.181.151.9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 2C483476DD for ; Fri, 21 Nov 2008 06:20:58 +1100 (EST) Date: Thu, 20 Nov 2008 20:20:09 +0100 From: Ingo Molnar To: Steven Rostedt Subject: Re: [PATCH 0/5] powerpc: dynamic ftrace port Message-ID: <20081120192009.GE3955@elte.hu> References: <20081120190948.057007623@goodmis.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Cc: Matt Fleming , linux-kernel@vger.kernel.org, Milton Miller , linuxppc-dev@ozlabs.org, Paul Mundt , Paul Mackerras , Andrew Morton , Thomas Gleixner List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , * Steven Rostedt wrote: > On Thu, 20 Nov 2008, Steven Rostedt wrote: > > > > 1) I removed the changes to recordmcount.pl. This is not a PowerPC > > change, although PowerPC needs it for dynamic ftrace. But > > the changes here can go via linux-tip. > > Ingo, > > I found that the recordmcount.pl change conflicts with a commit in > linux-next, which is not in tip nor mainline. The commit is: > > 11ebca4a3f8337de2f4d1300bd307851d1191d53 > sh: dynamic ftrace support. > > Seems that this change came in through the sh repo. I have already > resolved the conflicts with my updates for PowerPC with this commit. > I can put this in a separate branch against linux-next if you like. > > I would like to get the changes to recordmcount.pl for PowerPC in > linux-next soon, so I can also add a small clean up of this code. > Jim Radfort has some updates as well for his port to arm. Could you please extract the sh bits from 11ebca4a so that we can apply it to tip/tracing/* standalone? It makes sense to carry it without having the other bits of the SH changes. It will collide in linux-next but it will be a same-content collision with an easy enough (perhaps even automatic) resolution. Ingo