From: Christoph Hellwig <hch@lst.de>
To: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: future of sounds/oss
Date: Thu, 11 May 2017 10:21:33 +0200 [thread overview]
Message-ID: <20170511082133.GA20304@lst.de> (raw)
Ho Jaroslav, hi Takashi,
do you know who still uses the sound/oss drivers and why? I've
recently been looking into getting rid of set_fs for using
copy_{from,to}_user and friends on kernel pointers, and the sound
code is a big abuser, both ALSA and the legacy OSS code.
But looking at the OSS code it's pretty grotty, and also appears
to be pretty much unmaintained except for global cleanups. Is there
any chance we could look into getting rid of it over the next few
merge windows or are there people that rely on it?
next reply other threads:[~2017-05-11 8:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 8:21 Christoph Hellwig [this message]
2017-05-11 8:46 ` future of sounds/oss Takashi Iwai
2017-05-11 8:46 ` [alsa-devel] " Takashi Iwai
2017-05-11 9:15 ` Christoph Hellwig
2017-05-11 9:15 ` [alsa-devel] " Christoph Hellwig
2017-05-11 20:21 ` Takashi Iwai
2017-05-11 20:21 ` [alsa-devel] " Takashi Iwai
2017-05-11 20:28 ` Linus Torvalds
2017-05-11 20:36 ` Randy Dunlap
2017-05-11 20:40 ` Takashi Iwai
2017-05-11 20:40 ` [alsa-devel] " Takashi Iwai
2017-05-12 7:03 ` Geert Uytterhoeven
2017-05-12 7:10 ` Takashi Iwai
2017-05-12 7:17 ` Geert Uytterhoeven
2017-05-12 7:27 ` Takashi Iwai
2017-05-12 7:30 ` Geert Uytterhoeven
2017-05-12 8:01 ` Takashi Iwai
2017-05-16 7:45 ` Geert Uytterhoeven
2017-05-16 8:44 ` Takashi Iwai
2017-05-12 8:28 ` John Paul Adrian Glaubitz
2017-05-11 10:01 ` Takashi Sakamoto
2017-05-11 10:36 ` Takashi Sakamoto
2017-05-11 12:14 ` 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=20170511082133.GA20304@lst.de \
--to=hch@lst.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.