On Fri, 9 Oct 2009 12:26:42 -0700 Greg KH <gregkh@xxxxxxx> 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. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
