From: Ricard Wanderlof <ricardw@axis.com>
To: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 0/7] Allwinner A64 digital audio codec fixes
Date: Fri, 28 Aug 2020 13:05:59 +0200 [thread overview]
Message-ID: <alpine.DEB.2.21.2008281300530.19501@lnxricardw1.se.axis.com> (raw)
In-Reply-To: <20200828104948.sdq2ftwiwyjhh3lc@gilmour.lan>
This caught my eye and brought up an issue I've been wondering about for
some time:
On Fri, 28 Aug 2020, Maxime Ripard wrote:
> On Sat, Jul 25, 2020 at 08:25:50PM -0500, Samuel Holland wrote:
> > ... some DAPM widgets still have incorrect or confusing names; those
> > and other issues will be fixed in later patch sets.
As a general and firm rule in the Linux kernel when it comes to upgrades
and fixes is "We do not break userspace". Which means that for instance an
application must not stop working after a kernel upgrade due to some API
changing.
So does this mean that the name of an ALSA control, once it's in the
mainline kernel, can never be changed, for whatever reason?
Or devicetree properties, does the same apply there? Say a property as a
confusing name, is it possible to change it at all?
Or are these things open to debate, depending on the severity and
consequences etc?
/Ricard
--
Ricard Wolf Wanderlof ricardw(at)axis.com
Axis Communications AB, Lund, Sweden www.axis.com
Phone +46 46 272 2016 Fax +46 46 13 61 30
prev parent reply other threads:[~2020-08-28 11:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 1:25 [PATCH 0/7] Allwinner A64 digital audio codec fixes Samuel Holland
2020-07-26 1:25 ` [PATCH 1/7] ASoC: dt-bindings: Add a new compatible for the A64 codec Samuel Holland
2020-07-31 20:20 ` Rob Herring
2020-07-26 1:25 ` [PATCH 2/7] ASoC: sun8i-codec: Fix DAPM to match the hardware topology Samuel Holland
2020-07-26 1:25 ` [PATCH 3/7] ASoC: sun8i-codec: Add missing mixer routes Samuel Holland
2020-07-26 1:25 ` [PATCH 4/7] ASoC: sun8i-codec: Add a quirk for LRCK inversion Samuel Holland
2020-07-26 1:25 ` [PATCH 5/7] ARM: dts: sun8i: a33: Update codec widget names Samuel Holland
2020-07-26 1:25 ` [PATCH 6/7] arm64: dts: allwinner: a64: " Samuel Holland
2020-07-26 1:25 ` [PATCH 7/7] arm64: dts: allwinner: a64: Update the audio codec compatible Samuel Holland
2020-08-18 16:54 ` [PATCH 0/7] Allwinner A64 digital audio codec fixes Mark Brown
2020-08-24 14:03 ` Maxime Ripard
2020-08-25 15:36 ` Mark Brown
2020-08-28 10:08 ` Maxime Ripard
2020-08-28 10:49 ` Maxime Ripard
2020-08-28 11:05 ` Ricard Wanderlof [this message]
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=alpine.DEB.2.21.2008281300530.19501@lnxricardw1.se.axis.com \
--to=ricardw@axis.com \
--cc=alsa-devel@alsa-project.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).