public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Endriss <o.endriss@gmx.de>
To: hermann pitton <hermann-pitton@arcor.de>
Cc: video4linux-list@redhat.com, Michael Krufky <mkrufky@linuxtv.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] TT S-1401 problem with kernel 2.6.24 ???
Date: Fri, 4 Apr 2008 02:32:32 +0200	[thread overview]
Message-ID: <200804040232.33855@orion.escape-edv.de> (raw)
In-Reply-To: <1207265002.3364.12.camel@pc08.localdom.local>

hermann pitton wrote:
> Am Donnerstag, den 03.04.2008, 01:38 +0200 schrieb hermann pitton:
> > Hi again,
> > 
> > Am Mittwoch, den 02.04.2008, 22:47 +0400 schrieb Andrew Junev:
> > > Hello Hermann,
> > > 
> > > Thanks a lot for this detailed explanation!
> > > I really appreciate your help!
> > > 
> > > One small question: does it mean that kernels 2.6.24.5 or 2.6.24.6
> > > _should_ have this patch already included?
> > > 
> > 
> > seems we hang in current stable kernel rules.
> > 
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=Documentation/stable_kernel_rules.txt;hb=HEAD
> > 
> > If we go back to 2.6.23 level, that patch might have less than 100 lines
> > with context, but we break the
> > 
> >  - It must fix only one thing
> > 
> > rule, since we break the 2.6.24 LifeView Trio DVB-S support too then.
> > 
> > Seems sombody with such a device should reopen the bug on Bugzilla ...
> > 
> 
> Hi Guys,
> 
> should we really let hang it like this on 2.6.24?
> 
> I'm not that happy with a recommendation for the distributions to pick
> something out of it.
> 
> If we should go back to 2.6.23 level, so far nobody seems to have
> realized a improvement for the LifeView Trio stuff, I'm not against it.
> 
> The changeset in question to revert is mercurial 6579.
> 
> If nobody else is interested and no comments, I also don't care anymore.

(Basically I don't care because I am tired of discussing kernel
politics.)

Imho a fix should be applied, no matter how many lines it has.
If that is not possible the offending patch should be reverted in
2.6.24.x.

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

  reply	other threads:[~2008-04-04  0:33 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 [this message]
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
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=200804040232.33855@orion.escape-edv.de \
    --to=o.endriss@gmx.de \
    --cc=hermann-pitton@arcor.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