public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Hunold <hunold@linuxtv.org>
To: Gerd Knorr <kraxel@bytesex.org>
Cc: Eyal Lebedinsky <eyal@eyal.emu.id.au>,
	Michael Hunold <hunold@convergence.de>,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Johannes Stezenbach <js@convergence.de>
Subject: Re: Linux 2.6.10-rc3 oops when 'modprobe -r dvb-bt8xx'
Date: Tue, 07 Dec 2004 21:34:41 +0100	[thread overview]
Message-ID: <41B613E1.2010602@linuxtv.org> (raw)
In-Reply-To: <87653ex9wy.fsf@bytesex.org>

Hi,

Am 12/07/04 19:03, Gerd Knorr schrieb:
> I somehow feel the best way to deal with that is to merge the
> redesigned frontend handing pending in -mm at the moment into Linus
> tree _now_, that should kill that whole class of bugs.

Johannes and I had agreed with Andrew that the redesigned frontend code 
should stay in -mm for now, because we expect that support for some 
cards is broken. We currently don't receive very much reports on the 
mailing list though.

> That may result in the dvb subsystem not being that stable in 2.6.10.
> But dvb not being rock solid in 2.6.10 will very likely happen anyway
> as the code currently in Linus' tree isn't very stable as well.  I
> think the chance that it gets even worse is small enougth that we can
> take the risk.
> 
> Additional bonus would be that we don't get bugreports for the old
> code base which is already obsolete (and nobody wants to work on
> because of that).
> 
> Michael?

I just spoke to Johannes and we agree with you, Gerd. The DVB changes 
can and should be merged from -mm now. There is a fair chance that the 
remaining issues with broken cards can be resolved before 2.6.10.

The code is in a good shape and only some small patches are missing from 
the LinuxTV.org CVS.

I can prepare a patch that fixes the support for some cards and other 
minor improvements tomorrow.

>   Gerd

CU
Michael.

  reply	other threads:[~2004-12-07 20:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-04  0:19 Linux 2.6.10-rc3 Linus Torvalds
2004-12-04  9:06 ` Soeren Sonnenburg
2004-12-04 17:06   ` Alex Romosan
2004-12-04 17:24     ` Ari Pollak
2004-12-04 17:40       ` Alex Romosan
2004-12-04 19:21         ` Ari Pollak
2004-12-04 21:17         ` Martin Josefsson
2004-12-04 21:37           ` Alex Romosan
2004-12-04 21:42             ` Martin Josefsson
2004-12-04 23:48               ` Paul Ionescu
2004-12-04 21:47         ` Giridhar Pemmasani
2004-12-04 13:35 ` Linux 2.6.10-rc3 oops when 'modprobe -r dvb-bt8xx' Eyal Lebedinsky
2004-12-05 10:15   ` Cal Peake
2004-12-05 11:51     ` Eyal Lebedinsky
2004-12-05 12:50       ` Cal Peake
2004-12-07 18:03   ` Gerd Knorr
2004-12-07 20:34     ` Michael Hunold [this message]
2004-12-07 21:55       ` Andrew Morton
2004-12-07 23:08         ` Gerd Knorr
2004-12-06 17:23 ` FS Corruption [Re: Linux 2.6.10-rc3] Kristofer T. Karas
2004-12-06 19:20 ` Linux 2.6.10-rc3 (compile stats) John Cherry

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=41B613E1.2010602@linuxtv.org \
    --to=hunold@linuxtv.org \
    --cc=akpm@osdl.org \
    --cc=eyal@eyal.emu.id.au \
    --cc=hunold@convergence.de \
    --cc=js@convergence.de \
    --cc=kraxel@bytesex.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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