From: Lee Revell <rlrevell@joe-job.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: gregkh@suse.de, NAGANO Daisuke <breeze.nagano@nifty.ne.jp>,
alan@lxorguk.ukuu.org.uk, sailer@ife.ee.ethz.ch,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, perex@suse.cz,
alsa-devel@alsa-project.org, James@superbug.demon.co.uk,
linux-sound@vger.kernel.org, zab@zabbo.net,
kyle@parisc-linux.org, parisc-linux@lists.parisc-linux.org,
jgarzik@pobox.com, Thorsten Knabe <linux@thorsten-knabe.de>,
zaitcev@yahoo.com, Christoph Eckert <ce@christeck.de>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [2.6 patch] schedule obsolete OSS drivers for removal (version 2)
Date: Tue, 09 Aug 2005 13:54:48 -0400 [thread overview]
Message-ID: <1123610089.8210.7.camel@mindpipe> (raw)
In-Reply-To: <20050809174906.GA4006@stusta.de>
On Tue, 2005-08-09 at 19:49 +0200, Adrian Bunk wrote:
> I'd deprecate them without moving them.
>
OK, I think that will still be slightly confusing becuase it comes
before Sound in the kernel config, but maybe the deprecated part will
make people think twice.
I think we should at least label these clearly as part of OSS. Users at
least seem to know that mixing OSS and ALSA modules is bad.
> I'll send a patch unless someone tells that any functionality of these
> drivers is lacking in ALSA.
OK. I'm almost positive there is no functionality missing, there have
not been any reports of people needing to use the OSS driver on any of
the ALSA lists.
Lee
next prev parent reply other threads:[~2005-08-09 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 15:32 [2.6 patch] schedule obsolete OSS drivers for removal (version 2) Adrian Bunk
2005-08-09 17:13 ` Lee Revell
2005-08-09 17:49 ` Adrian Bunk
2005-08-09 17:54 ` Lee Revell [this message]
2005-08-12 19:58 ` Lee Revell
2005-08-14 11:00 ` [2.6 patch] schedule OSS USB drivers for removal Adrian Bunk
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=1123610089.8210.7.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=James@superbug.demon.co.uk \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=breeze.nagano@nifty.ne.jp \
--cc=bunk@stusta.de \
--cc=ce@christeck.de \
--cc=gregkh@suse.de \
--cc=jgarzik@pobox.com \
--cc=kyle@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linux@thorsten-knabe.de \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=perex@suse.cz \
--cc=sailer@ife.ee.ethz.ch \
--cc=zab@zabbo.net \
--cc=zaitcev@yahoo.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