public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
	tiwai@suse.com, perex@perex.cz
Subject: on (not) breaking user space
Date: Sun, 9 Jul 2023 14:32:03 +0200	[thread overview]
Message-ID: <ZKqow+jPg4HGyV6R@ugly> (raw)

hi linus,

the alsa maintainers seem to be applying a reading of "we don't break 
user space" that i find counter-productive. so i would appreciate you 
clarifying your position on that matter (once more ...)

to be clear, we're not arguing over changing any abi, but simply 
exercising one somewhat more than before. the claim is that this would 
likely have unacceptable consequences. i disagree.

context:
> Due to hardware constraints, changing the clock multiplier (CM) 
> changes the available audio ports and the number of available 
> channels. [...] Therefore, we do dynamic reconfiguration (DR) of the 
> mixer in response to changing the CM.

arguments:
> DR is somewhat controversial, as it has the potential to crash poorly 
> programmed applications.
> But that in itself isn't a very convincing argument against it, as by 
> that logic we'd have to ban all hot-plugging. (1)
> Such crashes would also not really qualify as regressions, as the 
> D.A.S. mode is a new opt-in feature, and therefore no previously 
> stable setups would be impacted. (2)

the full text is at 
https://lore.kernel.org/all/20230630144542.664190-7-oswald.buddenhagen@gmx.de/

the preceding discussion is at 
https://lore.kernel.org/all/87v8fren1k.wl-tiwai@suse.de/T/#u

regards,
ossi

                 reply	other threads:[~2023-07-09 12:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ZKqow+jPg4HGyV6R@ugly \
    --to=oswald.buddenhagen@gmx.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=torvalds@linux-foundation.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