Re: [v4l-dvb-maintainer] [PATCH 00/33] V4L/DVB bug fixes

From: hermann pitton
Date: Sun May 21 2006 - 19:05:47 EST

Am Sonntag, den 21.05.2006, 13:33 -0400 schrieb Michael Krufky:
> hermann pitton wrote:
> >Am Samstag, den 20.05.2006, 15:34 -0400 schrieb Michael Krufky:
> >
> >
> >>mchehab@xxxxxxxxxxxxx wrote:

> >
> >
> Hermann,
> The bugfixes that I am concerned about do not include the refactoring
> changes from Andrew -- those are not even bugfixes at all, and they are
> only accessible through our mercurial tree. We do not plan to send
> those upstream until 2.6.18 -- This has nothing at all to do with
> Mauro's latest git-pull-request, or my email to Linus.
> >At least, and thanks again for calming me down once, it is not about
> >some white space only now.
> >
> I'm not sure what you mean. Sure, we do have some drastic changes
> coming up for 2.6.18 ... but this email is about bugfixes that HAVE in
> fact been thoroughly tested.
> It sounds to me as if you may be getting the pending changesets in
> Mauro's git tree confused with current changes in our mercurial
> development repository.
> Just take a look at v4l-dvb.git ... (or at the diffstat earlier in
> this thread) .. You will find that the drastic changes that you have
> mentioned aren't there yet. Those do need some more testing before
> being sent upstream... I think they'll be ready in time for the 2.6.18
> merge window, but this is not the issue right now.
> Thanks for your concern,



for some users it will really look like broken multimedia on 2.6.17 like
you said. I don't worry to send them to something else then, but it
would really be nice to get the obvious fixes in or a hint, why it is
too late or so.

The mixture of a for some broken 2.6.17 and a upcoming 2.6.18 with huge
changes and a maybe too small testing base could become funny.

But yes, as you said, it are only concerns for now.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at