Re: Summary of REGRESSIONS which are being ignored?! (Re: Summaryof the pending patches up to Dec, 31 (26 patches))
From: Mauro Carvalho Chehab
Date: Mon Jan 03 2011 - 06:49:34 EST
Em 02-01-2011 17:30, Andy Walls escreveu:
> I don't see this patch on it's way upstream:
>
> https://patchwork.kernel.org/patch/376612/ (Sent on 5 Dec 2010)
> http://www.spinics.net/lists/linux-media/msg26649.html (Resent on 19 Dec 2010)
>
> It fixes a regression in IR and Analog video for cx23885 based cards and
> an intermittent analog video regression in ivtv based cards in 2.6.36
> and soon in 2.6.37.
Not sure what happened here. I'm sure I've applied on my fixes tree.
Anyway, I'm re-applying it.
> I emailed the LMML, you, and the author, as soon as I verified the root
> cause on 31 Dec, and haven't heard from from anyone:
>
> http://www.spinics.net/lists/linux-media/msg27261.html
Here, Dec, 31 is a national holiday. People work only half of the day.
Yet, I was finishing some things and preparing patches for the incoming
window, until afternoon.
I only noticed your email today, and I'm promptly sending it upstream,
together with a patch revert for wm8775 regression.
> Please revert it before the merge window closes.
I'm sending it right now.
> <rant>
> I have no time to make improvements that I want to make, much less waste
> my *VOLUNTEER* time on *REGRESSIONS* that *I DID NOT INTRODUCE*.
>
> It bothers me enough, that as a volunteer, I have to clean up other
> people's untested cr*pware. AND, that as the lucky individual who finds
> the bugs, I have to do additional work to get fixes back into stable
> kernels.
Shit happens. A patch adding support for one board might cause regression on
other boards, as it is not likely that the author of the patch have all
boards that could potentially be affected. That's why we have a long rc
period, where people with different hardware are expected to test the -rc
kernels and point for regressions.
Mauro.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/