On Mon, 05 May 2008 16:55:01 -0700 (PDT) David Miller <davem@davemloft.net> wrote:

quoted text
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Tue, 6 May 2008 09:51:22 +1000
> 
> > I (and I assume Andrew) have been carrying them since then but noone took
> > them up.  I guess (as Andrew pointed out to me) I should have pushed them.
> 
> So what should I do now?
>
> I have Ingo's IRDA PNP fixes in my net-2.6 tree and that's already
> publicly visible, so I'd need to add revert changesets if people want
> me to remove it.

Uncharted territory here.

As we discussed last week, I won't carry these patches because they're
already upstream.  It turns out that "upstream" in this case is linux-next
itself, which is an unexpected place for patches to be mastered.

So I suggest that Stephen send patches such as this into Linus sooner
rather than later.  Because nobody else will.

Well.  They _might_.  In this case Len could merge the patch in which case
Stephen would drop it and the fix would dawdle around in the acpi tree for
a while.

Ho hum, hopefully this isn't a common case.  Often Linus or I will just do
a maintainer bypass on things like this, but my ability to do that is now
much reduced because a) I can't merge the patch and b) when I _do_ try to
do that, it's "huh, we already fixed it".

So... I hereby appoint Stephen random-build-fix-monkey.
--
unsubscribe notice
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/