From: Takashi Iwai <tiwai@suse.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
perex@suse.cz, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: [Alsa-devel] [2.6 patch] sound/isa/: possible cleanups
Date: Fri, 13 May 2005 16:32:55 +0200 [thread overview]
Message-ID: <s5hd5rvryaw.wl@alsa2.suse.de> (raw)
In-Reply-To: <20050513140053.GF16549@stusta.de>
At Fri, 13 May 2005 16:00:53 +0200,
Adrian Bunk wrote:
>
>
> This patch was already sent on:
> - 9 Mar 2005
Yes, I remember.
The unused stuff in sound/isa/gus/* are for (everlasting :) future
development, e.g. WaveTable synth support. So I don't think it's a
good idea to remove completely them.
The clean up of wavefront_fx.c was already performed on ALSA tree but
seems not merged yet in the mainstream.
Takashi
next prev parent reply other threads:[~2005-05-13 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 14:00 [2.6 patch] sound/isa/: possible cleanups Adrian Bunk
2005-05-13 14:32 ` Takashi Iwai [this message]
2005-05-13 14:37 ` [Alsa-devel] " Adrian Bunk
2005-05-13 15:04 ` Takashi Iwai
2005-05-21 0:04 ` [2.6 patch] sound/isa/: cleanups Adrian Bunk
2005-05-23 9:30 ` Takashi Iwai
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=s5hd5rvryaw.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=akpm@osdl.org \
--cc=alsa-devel@alsa-project.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
/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