From: Randy Dunlap <rdunlap@infradead.org>
To: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Cc: Linus Torvalds <torvalds@linuxfoundation.org>,
linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2] sound: Disable the build of OSS drivers
Date: Thu, 11 May 2017 16:50:36 -0700 [thread overview]
Message-ID: <b2e30dfe-78a2-2d9f-5b0c-e60188a018bb@infradead.org> (raw)
In-Reply-To: <20170511205827.16446-1-tiwai@suse.de>
On 05/11/17 13:58, Takashi Iwai wrote:
> OSS drivers are left as badly unmaintained, and now we're facing a
> problem to clean up the hackish set_fs() usage in their codes. Since
> most of drivers have been covered by ALSA, and the others are dead old
> and inactive, let's leave them RIP.
>
> This patch is the first step: disable the build of OSS drivers.
> We'll eventually drop the whole codes and clean up later.
>
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
> ---
>
> v1->v2: Smaller changes, as Linus and Randy suggested.
> The first dmasound Kconfig inclusion is still commented out since
> it's shorter/simpler in the end.
>
> sound/Kconfig | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/sound/Kconfig b/sound/Kconfig
> index ee2e69a9ecd1..de23fc39cec8 100644
> --- a/sound/Kconfig
> +++ b/sound/Kconfig
> @@ -54,7 +54,7 @@ config SOUND_OSS_CORE_PRECLAIM
>
> If unsure, say Y.
>
> -source "sound/oss/dmasound/Kconfig"
> +# source "sound/oss/dmasound/Kconfig"
>
> if !M68K && !UML
>
> @@ -115,6 +115,7 @@ endif # SND
> menuconfig SOUND_PRIME
> tristate "Open Sound System (DEPRECATED)"
> select SOUND_OSS_CORE
> + depends on BROKEN
> help
> Say 'Y' or 'M' to enable Open Sound System drivers.
>
>
--
~Randy
next prev parent reply other threads:[~2017-05-11 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 20:58 [PATCH v2] sound: Disable the build of OSS drivers Takashi Iwai
2017-05-11 23:50 ` Randy Dunlap [this message]
2017-05-12 7:04 ` Geert Uytterhoeven
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=b2e30dfe-78a2-2d9f-5b0c-e60188a018bb@infradead.org \
--to=rdunlap@infradead.org \
--cc=alsa-devel@alsa-project.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=torvalds@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).