public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Greg KH <gregkh@suse.de>
Cc: 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>
Subject: Re: [GIT PULL] omap fixes for v2.6.32-rc3
Date: Fri, 9 Oct 2009 14:33:27 -0700	[thread overview]
Message-ID: <20091009143327.783b33c3.akpm@linux-foundation.org> (raw)
In-Reply-To: <20091009192642.GB32084@suse.de>

On Fri, 9 Oct 2009 12:26:42 -0700
Greg KH <gregkh@suse.de> wrote:

> > >
> > > What kind of issues? __Why would I be interested, where is the problem?
> > 
> > The obvious-brain-dead-duh kind of issues, like this one.
> > 
> > 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?
> 
> > To me it's not clear who should push the patch, it seems it doesn't
> > belong on linux-omap, so Tony is pushing it through linux-mmc, which I
> > don't think is the right place. They should be handling mmc-related
> > issues, not obvious breakage.
> 
> Well, mmc related breakage is fine to handle :)
> 
> > In order to keep the engines oiled I think there must be a process to
> > flag obvious generic breakage so it's immediately picked; maybe an
> > 'obvious-fixes' tree, or a 'simple-fixes' that has 'trivial',
> > 'includecheck', and similar, or maybe nothing needs to be done. Up to
> > you to decide.
> 
> Andrew usually sends stuff like this at times.

yeah, when in doubt, send it to me.  When not in doubt send it to me
anyway ;)

I'll take care of bugging the appropriate maintainer or merging it directly.

  reply	other threads:[~2009-10-09 21:33 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 [this message]
2009-10-10 10:38                     ` Felipe Contreras
2009-10-09 21:42                   ` Jiri Kosina
2009-10-09 21:57                     ` Andrew Morton
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=20091009143327.783b33c3.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=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --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