public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@convergence.de>
To: Florian Huber <florian.huber@mnet-online.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Tuning (stv0299.ko) with SkyStar2/DVB not working with 2.6.8-rc* anymore
Date: Thu, 5 Aug 2004 18:54:31 +0200	[thread overview]
Message-ID: <20040805165431.GE2080@convergence.de> (raw)
In-Reply-To: <1091574593.24571.13.camel@suprafluid.huber.lan>

On Wed, Aug 04, 2004 at 01:09:53AM +0200, Florian Huber wrote:
> My problem seems to be solved with some 2.6.8-rc2-mm2 and 2.6.8-rc3.
> 
> But the major device node change from 250 to 212 should be emphasized.
> Without the obsolete devfs it is not that easy to find out the new
> device node for an average user.

It's announced prominently on http://linuxtv.org/, and was
listed in the Changelog on kernel.org. What more can we do?

Johannes

      reply	other threads:[~2004-08-05 16:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-25 10:20 Tuning (stv0299.ko) with SkyStar2/DVB not working with 2.6.8-rc* anymore Florian Huber
2004-08-03 23:09 ` Florian Huber
2004-08-05 16:54   ` Johannes Stezenbach [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=20040805165431.GE2080@convergence.de \
    --to=js@convergence.de \
    --cc=florian.huber@mnet-online.de \
    --cc=linux-kernel@vger.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