linux-kernel - Re: 2.6.27.40 build error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <37219a840912081620r1d34a13dpf3a36f83f82c9a67@mail.gmail.com>
Date:	Tue, 8 Dec 2009 19:20:24 -0500
From:	Michael Krufky <mkrufky@...nellabs.com>
To:	Devin Heitmueller <dheitmueller@...nellabs.com>
Cc:	Greg KH <greg@...ah.com>,
	Mauro Carvalho Chehab <mchehab@...hat.com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	linux-kernel@...r.kernel.org, stable@...nel.org
Subject: Re: 2.6.27.40 build error

On Tue, Dec 8, 2009 at 6:11 PM, Devin Heitmueller
<dheitmueller@...nellabs.com> wrote:
> On Tue, Dec 8, 2009 at 6:02 PM, Michael Krufky <mkrufky@...nellabs.com> wrote:
>> Yes -- please drop it for now.  I didn't actually send this for
>> 2.6.27.y anyway -- it must have gotten to you some other way.
>>
>> Devin, if 2.6.27.y needs this fix, can you please generate the
>> appropriate backport and test it before we resubmit?
>
> We would have to decide whether it's worth the effort to get a 2.6.27
> environment setup to do the necessary regression testing.  At this
> point, I would argue that driver was screwed up enough in 2.6.27 that
> I wouldn't be inclined to tell users it worked even with this one fix.
>
> Devin

Fine with me -- I'm glad the v4l-dvb development repositories hosted
on both linuxtv.org and kernellabs.com are backwards compatible with
recent kernels... :-)

I think all the crucial fixes (except for the pvrusb2 16k firmware
patch) are all merged into 2.6.31.y as of now... So, now we can focus
on new driver support for 2.6.32 :-)

Cheers,

Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/