From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758765AbaELQPs (ORCPT ); Mon, 12 May 2014 12:15:48 -0400 Received: from cam-admin0.cambridge.arm.com ([217.140.96.50]:49188 "EHLO cam-admin0.cambridge.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751159AbaELQPn (ORCPT ); Mon, 12 May 2014 12:15:43 -0400 Date: Mon, 12 May 2014 17:12:46 +0100 From: Will Deacon To: Steven Rostedt Cc: AKASHI Takahiro , "fweisbec@gmail.com" , "mingo@redhat.com" , Catalin Marinas , "tim.bird@sonymobile.com" , "gkulkarni@caviumnetworks.com" , "dsaxena@linaro.org" , "arndb@arndb.de" , "linux-arm-kernel@lists.infradead.org" , "linaro-kernel@lists.linaro.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH v8 1/8] ftrace: make CALLER_ADDRx macros more generic Message-ID: <20140512161246.GC4880@arm.com> References: <1394862048-28758-1-git-send-email-takahiro.akashi@linaro.org> <1398851676-16389-1-git-send-email-takahiro.akashi@linaro.org> <1398851676-16389-2-git-send-email-takahiro.akashi@linaro.org> <20140502151957.6978d870@gandalf.local.home> <20140512155811.GB4880@arm.com> <20140512120535.041030dd@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140512120535.041030dd@gandalf.local.home> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hey Steve, On Mon, May 12, 2014 at 05:05:35PM +0100, Steven Rostedt wrote: > On Mon, 12 May 2014 16:58:11 +0100 > Will Deacon wrote: > > > Akashi: did you get around to posting a new version of this patch? We can't > > take your arm64 patches until you get the core stuff merged... > > I haven't seen any patches yet. > > What I can also do is to create a separate branch based on mainline, > and just apply this change to the core. Then you could pull that branch > with a note to Linus that it is also in my tree with the common > ancestor. > > If he pulls your work first, he'll only get that change from my tree, > and if he pulls mine first it doesn't matter as all the changes will be > there. > > This is something he said at Kernel Summit that was normal procedure if > there's a change in one tree that another tree is dependent on. That sounds great, and nicely solves the dependency between our trees for 3.16 at the same time. If you point us at the branch and promise not to rebase it, that would be fantastic. Cheers, Will From mboxrd@z Thu Jan 1 00:00:00 1970 From: will.deacon@arm.com (Will Deacon) Date: Mon, 12 May 2014 17:12:46 +0100 Subject: [PATCH v8 1/8] ftrace: make CALLER_ADDRx macros more generic In-Reply-To: <20140512120535.041030dd@gandalf.local.home> References: <1394862048-28758-1-git-send-email-takahiro.akashi@linaro.org> <1398851676-16389-1-git-send-email-takahiro.akashi@linaro.org> <1398851676-16389-2-git-send-email-takahiro.akashi@linaro.org> <20140502151957.6978d870@gandalf.local.home> <20140512155811.GB4880@arm.com> <20140512120535.041030dd@gandalf.local.home> Message-ID: <20140512161246.GC4880@arm.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hey Steve, On Mon, May 12, 2014 at 05:05:35PM +0100, Steven Rostedt wrote: > On Mon, 12 May 2014 16:58:11 +0100 > Will Deacon wrote: > > > Akashi: did you get around to posting a new version of this patch? We can't > > take your arm64 patches until you get the core stuff merged... > > I haven't seen any patches yet. > > What I can also do is to create a separate branch based on mainline, > and just apply this change to the core. Then you could pull that branch > with a note to Linus that it is also in my tree with the common > ancestor. > > If he pulls your work first, he'll only get that change from my tree, > and if he pulls mine first it doesn't matter as all the changes will be > there. > > This is something he said at Kernel Summit that was normal procedure if > there's a change in one tree that another tree is dependent on. That sounds great, and nicely solves the dependency between our trees for 3.16 at the same time. If you point us at the branch and promise not to rebase it, that would be fantastic. Cheers, Will