public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Greg KH <gregkh@suse.de>,
	Felipe Contreras <felipe.contreras@gmail.com>,
	Tony Lindgren <tony@atomide.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
	Denis Karpov <ext-denis.2.karpov@nokia.com>,
	Uwe Kleine-K??nig <u.kleine-koenig@pengutronix.de>,
	Madhusudhan Chikkature <madhu.cr@ti.com>
Subject: Re: [GIT PULL] omap fixes for v2.6.32-rc3
Date: Fri, 9 Oct 2009 14:57:24 -0700	[thread overview]
Message-ID: <20091009145724.24614ccd.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LRH.2.00.0910092336280.12171@twin.jikos.cz>

On Fri, 9 Oct 2009 23:42:27 +0200 (CEST)
Jiri Kosina <jkosina@suse.cz> wrote:

> 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.

hm.  What's all the fuss about?  That patch was sent To:me and affects
only MMC and is clearly a bugfix.  I'll merge it when i get to it
(hopefully tomorrow) then all is good?


  reply	other threads:[~2009-10-09 21:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-07 18:51 [GIT PULL] omap fixes for v2.6.32-rc3 Tony Lindgren
2009-10-08 21:29 ` Felipe Contreras
2009-10-08 21:41   ` Tony Lindgren
2009-10-08 22:13     ` Felipe Contreras
2009-10-08 22:20       ` Felipe Contreras
2009-10-08 23:26         ` Tony Lindgren
2009-10-09 12:08           ` Felipe Contreras
2009-10-09 14:48             ` Greg KH
2009-10-09 17:29               ` Felipe Contreras
2009-10-09 19:26                 ` Greg KH
2009-10-09 21:33                   ` Andrew Morton
2009-10-10 10:38                     ` Felipe Contreras
2009-10-09 21:42                   ` Jiri Kosina
2009-10-09 21:57                     ` Andrew Morton [this message]
2009-10-09 22:32                     ` Madhusudhan
2009-10-09  8:02       ` Uwe Kleine-König
2009-10-09  8:25         ` Felipe Contreras
2009-10-09  8:30           ` Uwe Kleine-König

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091009145724.24614ccd.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=ext-denis.2.karpov@nokia.com \
    --cc=felipe.contreras@gmail.com \
    --cc=gregkh@suse.de \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=madhu.cr@ti.com \
    --cc=tony@atomide.com \
    --cc=torvalds@linux-foundation.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox