From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: MMC maintainer Date: Fri, 10 Sep 2010 13:58:24 -0700 Message-ID: <20100910135824.a4cb1f44.akpm@linux-foundation.org> References: <20100909114750.09214854.akpm@linux-foundation.org> <20100910201419.GA2623@void.printf.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from smtp1.linux-foundation.org ([140.211.169.13]:52994 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753835Ab0IJU65 (ORCPT ); Fri, 10 Sep 2010 16:58:57 -0400 In-Reply-To: <20100910201419.GA2623@void.printf.net> Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Chris Ball Cc: linux-mmc@vger.kernel.org On Fri, 10 Sep 2010 21:14:19 +0100 Chris Ball wrote: > On Thu, Sep 09, 2010 at 11:47:50AM -0700, Andrew Morton wrote: > > These things can happen in parallel - get the tree set up, get it into > > linux-next, start putting patches in it. If I see patches turn up in > > linux-next which I already have, I just drop them. If I find I'm > > holding patches which should be in the mmc tree but which aren't, I > > send them to you. > > Thanks -- have created the tree, added its mmc-next branch to -next, and > started pushing to it (location below). Here's a MAINTAINERS update: > > Subject: mmc: add MAINTAINERS entry > > Add myself as maintainer. Kewl. Please work with Stephen on getting that into linux-next.