mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: Christoph Hellwig <hch@lst.de>, Jaroslav Kysela <perex@perex.cz>,
	Linus Torvalds <torvalds@linuxfoundation.org>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] future of sounds/oss
Date: Thu, 11 May 2017 11:15:11 +0200	[thread overview]
Message-ID: <20170511091511.GA21055@lst.de> (raw)
In-Reply-To: <s5hh90rhjbc.wl-tiwai@suse.de>

On Thu, May 11, 2017 at 10:46:47AM +0200, Takashi Iwai wrote:
> Yeah, I also started looking at it after reading the LWN article.
> The removal of set_fs() in ALSA part was already finished, and I'm
> currently brushing up the patches.  It'll be in 4.13 at latest.

Great!

> That said, I'd love to drop that legacy stuff; or maybe as a
> soft-landing, begin with disabling the build of sound/oss in Kconfig.
> 
> The latter can be done even for 4.12, if Linus doesn't mind.

I'd be absolutely in favor of trying that and seeing if anyone
screams.

  reply	other threads:[~2017-05-11  9:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11  8:21 Christoph Hellwig
2017-05-11  8:46 ` [alsa-devel] " Takashi Iwai
2017-05-11  9:15   ` Christoph Hellwig [this message]
2017-05-11 20:21     ` 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-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=20170511091511.GA21055@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.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

Powered by JetHome