From: Oliver Endriss <o.endriss@gmx.de>
To: mkrufky@linuxtv.org
Cc: video4linux-list@redhat.com, mchehab@infradead.org,
linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] TT S-1401 problem with kernel 2.6.24 ???
Date: Wed, 9 Apr 2008 00:27:18 +0200 [thread overview]
Message-ID: <200804090027.19735@orion.escape-edv.de> (raw)
In-Reply-To: <47FBDD42.2030608@linuxtv.org>
mkrufky@linuxtv.org wrote:
> ...
> ...all of this noise was made, and now not a single person is willing to
> test the proposed solution?
>
> I don't think that there will be many more 2.6.24.y releases. I have an
> ivtv patch queued for 2.6.24.5, and this tda10086 patch is sitting in my
> outbox, waiting for test results.
>
> I suspect that 2.6.25 will be released in a few days, after which,
> 2.6.24.y -stable release turnaround gets slower and slower, and most
> likely will end by the time 2.6.26 is released.
>
> If you want this fixed, then the fix needs testing .... NOW.
Always the same story. :-(
We need a test center, or preferably a community of testers who are
willing to do regression tests with the drivers...
CU
Oliver
--
----------------------------------------------------------------
VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
----------------------------------------------------------------
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-04-08 22:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 20:36 [linux-dvb] TT S-1401 problem with kernel 2.6.24 ??? Andrew Junev
2008-03-19 23:48 ` Oliver Endriss
2008-03-20 18:23 ` Andrew Junev
2008-03-21 2:37 ` hermann pitton
2008-03-21 6:42 ` Oliver Endriss
2008-03-21 18:29 ` Andrew Junev
[not found] ` <1206912674.3520.58.camel@pc08.localdom.local>
[not found] ` <1063704330.20080331082850@a-j.ru>
[not found] ` <1206999694.7762.41.camel@pc08.localdom.local>
[not found] ` <1112443057.20080402224744@a-j.ru>
2008-04-02 23:38 ` hermann pitton
2008-04-03 23:23 ` hermann pitton
2008-04-04 0:32 ` Oliver Endriss
2008-04-04 0:43 ` hermann pitton
[not found] ` <20080403222937.3b234a40@gaivota>
2008-04-04 2:56 ` Oliver Endriss
2008-04-04 4:14 ` Michael Krufky
2008-04-04 11:44 ` Mauro Carvalho Chehab
2008-04-04 12:56 ` Michael Krufky
2008-04-04 13:23 ` Michael Krufky
2008-04-04 17:59 ` Oliver Endriss
2008-04-04 23:08 ` hermann pitton
2008-04-08 21:01 ` mkrufky
2008-04-08 22:10 ` hermann pitton
2008-04-08 22:27 ` Oliver Endriss [this message]
2008-04-08 22:36 ` Mauro Carvalho Chehab
2008-04-04 12:02 ` Oliver Endriss
[not found] ` <20080403221833.34d3c4d6@gaivota>
2008-04-04 2:19 ` hermann pitton
[not found] ` <1076827621.20080406215420@a-j.ru>
[not found] ` <1207522685.6334.29.camel@pc08.localdom.local>
[not found] ` <1135983778.20080408193408@a-j.ru>
2008-04-09 0:56 ` hermann pitton
2008-04-09 6:17 ` Andrew Junev
2008-04-09 23:03 ` hermann pitton
2008-05-13 15:55 ` Andrew Junev
2008-05-15 0:23 ` hermann pitton
2008-04-04 14:15 ` ldvb
2008-04-04 14:17 ` ldvb
2008-04-04 23:20 ` hermann pitton
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=200804090027.19735@orion.escape-edv.de \
--to=o.endriss@gmx.de \
--cc=linux-dvb@linuxtv.org \
--cc=mchehab@infradead.org \
--cc=mkrufky@linuxtv.org \
--cc=video4linux-list@redhat.com \
/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