Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752918AbZFYUqq (ORCPT ); Thu, 25 Jun 2009 16:46:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751897AbZFYUqj (ORCPT ); Thu, 25 Jun 2009 16:46:39 -0400 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:56136 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750964AbZFYUqj (ORCPT ); Thu, 25 Jun 2009 16:46:39 -0400 Date: Thu, 25 Jun 2009 21:46:30 +0100 From: Russell King - ARM Linux To: Brian Swetland Cc: Pavel Machek , linux-arm-kernel@lists.arm.linux.org.uk, linux-kernel@vger.kernel.org Subject: Re: [PATCH 3/3] [ARM] msm: add minimal board file for HTC Dream device Message-ID: <20090625204630.GH11875@n2100.arm.linux.org.uk> References: <1245033557-10968-2-git-send-email-swetland@google.com> <1245033557-10968-3-git-send-email-swetland@google.com> <1245033557-10968-4-git-send-email-swetland@google.com> <20090615132248.GB14555@elf.ucw.cz> <20090615182850.GA10490@elf.ucw.cz> <20090624205618.GD9149@elf.ucw.cz> <20090625135532.GB11875@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1740 Lines: 37 On Thu, Jun 25, 2009 at 12:31:03PM -0700, Brian Swetland wrote: > On Thu, Jun 25, 2009 at 6:55 AM, Russell King - ARM > Linux wrote: > > On Wed, Jun 24, 2009 at 10:56:19PM +0200, Pavel Machek wrote: > >> Are there any issues that prevent this from being merged? Russell, can > >> you take those patches? > > > > I thought Alan's preference was for me to be out of the loop on machine > > specific stuff, and for platform maintainers to push their stuff directly > > into linux-next and to Linus. > > > > If people do want to push stuff via me, that's fine, but they're going to > > have to explicitly ask for it. ?If they don't, that's also fine. ?(There > > are those who clearly stated that they want my continued involvement and > > review.) > > I wasn't sure when/how the process would change here. Could somebody > point me at any up to date information on how/where to send stuff to > linux-next? Documentation/development-process/2.Process, last bits of section 2.4. > I'm still interested in sending patches past lakml/lkml for review > though -- I've received very useful feedback from previous patches > this way in the past. Presumably (for arch/arm/mach-msm/...) I could > send patch series out for review, adjust them as necessary based on > feedback, and assemble into a git branch suitable for linux-next? Still happy to do that. linux-next only takes git branches, and when you talk to sfr he'll tell you about what he wants to see in that branch. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/