From: Michael Krufky <mkrufky@kernellabs.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Greg KH <greg@kroah.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: 2.6.27.40 build error
Date: Tue, 8 Dec 2009 19:20:24 -0500 [thread overview]
Message-ID: <37219a840912081620r1d34a13dpf3a36f83f82c9a67@mail.gmail.com> (raw)
In-Reply-To: <829197380912081511k2ad53053t1a1f73b6e8571f75@mail.gmail.com>
On Tue, Dec 8, 2009 at 6:11 PM, Devin Heitmueller
<dheitmueller@kernellabs.com> wrote:
> On Tue, Dec 8, 2009 at 6:02 PM, Michael Krufky <mkrufky@kernellabs.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
prev parent reply other threads:[~2009-12-09 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 21:42 Greg KH
2009-12-08 21:49 ` Devin Heitmueller
2009-12-08 23:01 ` Greg KH
2009-12-08 23:02 ` Michael Krufky
2009-12-08 23:11 ` Devin Heitmueller
2009-12-09 0:20 ` Michael Krufky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37219a840912081620r1d34a13dpf3a36f83f82c9a67@mail.gmail.com \
--to=mkrufky@kernellabs.com \
--cc=dheitmueller@kernellabs.com \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=stable@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®