From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1755301AbdEKIVh (ORCPT <rfc822;w@1wt.eu>);
        Thu, 11 May 2017 04:21:37 -0400
Received: from verein.lst.de ([213.95.11.211]:53660 "EHLO newverein.lst.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1755272AbdEKIVf (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 11 May 2017 04:21:35 -0400
Date: Thu, 11 May 2017 10:21:33 +0200
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
Message-ID: <20170511082133.GA20304@lst.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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?