Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761533AbZJIVnI (ORCPT ); Fri, 9 Oct 2009 17:43:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761505AbZJIVnH (ORCPT ); Fri, 9 Oct 2009 17:43:07 -0400 Received: from cantor2.suse.de ([195.135.220.15]:35190 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761453AbZJIVnF (ORCPT ); Fri, 9 Oct 2009 17:43:05 -0400 Date: Fri, 9 Oct 2009 23:42:27 +0200 (CEST) From: Jiri Kosina X-X-Sender: jikos@twin.jikos.cz To: Greg KH Cc: Felipe Contreras , Tony Lindgren , Linus Torvalds , linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, Denis Karpov , Uwe Kleine-K??nig , Andrew Morton , Madhusudhan Chikkature Subject: Re: [GIT PULL] omap fixes for v2.6.32-rc3 In-Reply-To: <20091009192642.GB32084@suse.de> Message-ID: References: <20091007185112.GJ7899@atomide.com> <94a0d4530910081429m7ad88b43q38245109f3252078@mail.gmail.com> <20091008214140.GJ7417@atomide.com> <94a0d4530910081513w1a919dc2s50eca41966a2261d@mail.gmail.com> <94a0d4530910081520t66ce7567xe142979a35b1245@mail.gmail.com> <20091008232603.GB25892@atomide.com> <94a0d4530910090508o1e3d19cew881d2eb348199674@mail.gmail.com> <20091009144840.GA9561@suse.de> <94a0d4530910091029p12f8c28fve91e95db533e78e5@mail.gmail.com> <20091009192642.GB32084@suse.de> User-Agent: Alpine 2.00 (LRH 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1322 Lines: 34 On Fri, 9 Oct 2009, Greg KH wrote: > > >> There's a tree for trivial fixes: > > >> git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial Well, as this is quite a high-priority functional fix, I'd suggest using other channels that trivial tree, as this one is primarily intended for simple fixes that are not really urgent. > > The problem is that OMAP devices (like beagleboard) are not booting > > correctly right now because of a wrong merge. It has been identified, > > tested, and acked, but nobody has picked it up for a pull request, so > > it's not clear it will be on -rc4. > Has the patches been sent from the maintainer to Linus? > Who is the maintainer? Who normally sends this stuff? The problem is that MMC now doesn't have proper maintainer, since Pierre stepped down from maintaining this stuff. Still, for the fix mentioned on http://www.mail-archive.com/linux-mmc@vger.kernel.org/msg00539.html the most appropriate contact would probably be Madhusudhan Chikkature. Adding him to CC of this thread. -- Jiri Kosina SUSE Labs, Novell Inc. -- 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/