From: Andrew Morton <akpm@osdl.org>
To: Michael Hunold <hunold@linuxtv.org>
Cc: kraxel@bytesex.org, eyal@eyal.emu.id.au, hunold@convergence.de,
torvalds@osdl.org, linux-kernel@vger.kernel.org,
js@convergence.de
Subject: Re: Linux 2.6.10-rc3 oops when 'modprobe -r dvb-bt8xx'
Date: Tue, 7 Dec 2004 13:55:21 -0800 [thread overview]
Message-ID: <20041207135521.4c04c102.akpm@osdl.org> (raw)
In-Reply-To: <41B613E1.2010602@linuxtv.org>
Michael Hunold <hunold@linuxtv.org> wrote:
>
> 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.
How much end-user testing has the new code had? ie: are we confident that
the new code is presently more stable than the old code?
> 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.
Yup, please start working on those things.
next prev parent reply other threads:[~2004-12-07 21:52 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
2004-12-07 21:55 ` Andrew Morton [this message]
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=20041207135521.4c04c102.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=eyal@eyal.emu.id.au \
--cc=hunold@convergence.de \
--cc=hunold@linuxtv.org \
--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
all inboxes | Powered by JetHome®