From: Christoph Hellwig <c0hellwi@rks.harz.ni.schule.de>
To: linux-sound@vger.kernel.org
Subject: Re: [PATCH] removal of legacy sound defines
Date: Fri, 25 Feb 2000 07:50:51 +0000 [thread overview]
Message-ID: <marc-linux-sound-95146779531327@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-95143229508229@msgid-missing>
Jeff Garzik wrote:
> Christoph Hellwig wrote:
> >
> > Hi, this patch removes all the sound (oss) legacy defines.
> > Since Alan modularized the oss code, the semed to be no new free
> > version of OSS, so it might be usefull to remove the legacy defines.
> This doesn't look like a good idea to me.... Have you analyzed all the
> paths and permutations for those config options you are chopping?
Yes, it's ok, they are all defined in thenoe obsolete header legacy.h.
Look at the file README.CONFIG that is removed by my patch.
Btw. When I get some more old sound cards to test it, I'll try to clean up the oss mess even more
and remove the compile-time selection of the resources.
Christoph
--
Always remember that you are unique. Just like everyone else.
prev parent reply other threads:[~2000-02-25 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-24 20:11 [PATCH] removal of legacy sound defines Christoph Hellwig
2000-02-24 23:58 ` Jeff Garzik
2000-02-25 1:48 ` Alan Cox
2000-02-25 7:50 ` Christoph Hellwig [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=marc-linux-sound-95146779531327@msgid-missing \
--to=c0hellwi@rks.harz.ni.schule.de \
--cc=linux-sound@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