From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brown Subject: Re: linux-next: manual merge of the msm tree with the arm tree Date: Fri, 04 Feb 2011 12:38:01 -0800 Message-ID: <8yawrlfzgba.fsf@huya.qualcomm.com> References: <20110131131401.5d6c7646.sfr@canb.auug.org.au> <8ya4o8m70jp.fsf@huya.qualcomm.com> <20110202194359.GC27065@kroah.com> <20110202200030.GA26104@flint.arm.linux.org.uk> <20110202203252.GD28479@kroah.com> <20110202204453.GB26104@flint.arm.linux.org.uk> <1296839855.4078.12.camel@m0nster> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from wolverine01.qualcomm.com ([199.106.114.254]:59547 "EHLO wolverine01.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751431Ab1BDUiC (ORCPT ); Fri, 4 Feb 2011 15:38:02 -0500 In-Reply-To: (Nicolas Pitre's message of "Fri, 04 Feb 2011 14:40:04 -0500 (EST)") Sender: linux-next-owner@vger.kernel.org List-ID: To: Nicolas Pitre Cc: Daniel Walker , Greg KH , Russell King , Stephen Rothwell , linux-next@vger.kernel.org, lkml , Stepan Moskovchenko , linux-arm-msm@vger.kernel.org On Fri, Feb 04 2011, Nicolas Pitre wrote: > Maybe this would be nicer to Russell and others performing wide ranging > changes to the ARM code if the msm tree was more visible downstream, and > potentially help to avoid making a mountain out of a mole hill. Currently, the msm tree is in linux-next, and the URL is in the MAINTAINER's file. The only want to make it more visible would be to give frequent pull requests to RMK, which would create extra work for him. I think I just need to come up with the right balance of how often to give the tree to RMK. David -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.