Re: [PULL] http://linuxtv.org/hg/~mkrufky/xc2028 | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
I can't believe that I managed to accidentally sent this from a bogus email account (again) ... Please see below for the content -- I apologize for sending this twice -- the first copy probably didn't make it to the mailing list. Michael Krufky wrote: >> On Tue, Sep 30, 2008 at 11:22 AM, Devin Heitmueller >> <devin.heitmueller@xxxxxxxxx> wrote: >>> Hello Mauro, >>> >>> As I'm sure you know, 2.6.27-rc8 just came out. I hate to keep >>> pestering you about this, but I would really rather not see a version >>> of the mainline kernel be released that's going to burn out people's >>> hardware. >>> >>> Is there *anything* I can do to get a git pull to happen for this fix >>> before the release? I know you're busy, but is there anyone else who >>> can do it if you don't have the cycles? >>> >>> Devin >>> >>> On Wed, Sep 24, 2008 at 11:25 AM, Mauro Carvalho Chehab >>> <mchehab@xxxxxxxxxxxxx> wrote: >>>> On Wed, 24 Sep 2008, Devin Heitmueller wrote: >>>> >>>>> I appreciate it. >>>>> >>>>> If it's any consolation, I actually now own the device in question and >>>>> was able to personally validate the fix (it isn't a fix tested by a >>>>> third-party like the original support I added was). It was also >>>>> tested by the user I originally added the support for. >>>> I don't doubt it is right. I just need time to prepare the >>>> changesets for >>>> upstream submission. I'm very busy here, with pending work, due to >>>> the time >>>> I was out at KS and LPC. >>>> >>>> Cheers, >>>> Mauro >>>> >>> >>> >>> -- >>> Devin J. Heitmueller >>> http://www.devinheitmueller.com >>> AIM: devinheitmueller >>> >> > Devin Heitmueller wrote: >> Hello Michael, >> >> I'm not sure if Mauro is away, but I emailed him a couple of days ago >> and hadn't heard anything. >> >> Is there anyone else would could get this Git pull to Linus? I >> believe 2.6.27 will go out any day (the email suggested -rc8 might be >> the last release), and I really don't want to see a release go out >> that will burn out people's hardware. >> >> Regards, >> >> Devin >> > > Devin, > > I've added cc to the v4l-dvb-maintainer mailing list, for the archives. > > Mauro, > > Are you around? Do you need me to send this to Linus, instead? 2.6.27 > might be released any day. > > We really need pending bugfixes to go upstream before 2.6.27 is released > -- it is not okay to just rely on the -stable kernel series for this > type of thing, especially when we actually have time to get it to Linus. > > This (-stable) is something that we can fall back on, for when we miss > the merge window, but this particular instance is not a case of missing > a merge window. We've had this patch in mercurial for more than a week, > and the email from Devin explaining the severity of this issue since > Tuesday -- If we don't get it to Linus on time, then it means that > somebody 'dropped the ball' > > This issue can cause the device in question to burn out. We should get > this fix upstream ASAP. > > If I don't hear from you by 6pm EDT tomorrow (Saturday 10/4) evening, I > will prepare the changeset to send to Linus myself. If you get this > email in the meanwhile and plan to send it yourself, please let me know > as soon as possible. > > > Regards, > > Mike > _______________________________________________ v4l-dvb-maintainer mailing list v4l-dvb-maintainer@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/v4l-dvb-maintainer
|
|
-->
