From: Greg KH <greg@kroah.com>
To: Mark Brown <broonie@kernel.org>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
johan+linaro@kernel.org, perex@perex.cz, tiwai@suse.com,
lgirdwood@gmail.com, ckeepax@opensource.cirrus.com,
kuninori.morimoto.gx@renesas.com, linux-kernel@vger.kernel.org,
pierre-louis.bossart@linux.intel.com,
alsa-devel@alsa-project.org, Stable@vger.kernel.org
Subject: Re: [PATCH] ASoC: qdsp6: q6apm: use dai link pcm id as pcm device number
Date: Thu, 29 Jun 2023 20:48:42 +0200 [thread overview]
Message-ID: <2023062905-tiring-bauble-84ef@gregkh> (raw)
In-Reply-To: <1c1dd19e-cbc4-41fe-9e97-a07cfebdaa4b@sirena.org.uk>
On Thu, Jun 29, 2023 at 06:38:38PM +0100, Mark Brown wrote:
> On Thu, Jun 29, 2023 at 07:22:51PM +0200, Greg KH wrote:
>
> > It shouldn't matter for stable or not, if the change is acceptable in
> > Linus's tree, with the userspace visable change, then it should be
> > acceptable in any active stable branch as well. There is no difference
> > here for userspace api/abi rules.
>
> As discussed before your tolerance for risk in stable is *far* higher
> than mine, if there's any value in doing this at all it's probably
> within what would get taken but that doesn't mean that it's something
> that it's sensible to highlight as an important fix like tagging for
> stable does. It's extremely unclear that it fits the severity criteria
> that are supposed to be being applied to stable, though obviously the
> documentation doesn't fit the actual practice these days.
It's not a matter of "tolerance for risk", it's a "if this change is
good enough for future releases, why isn't it good enough for older
releases as well?"
As you know, we don't break user interfaces, so either this is a break
or it isn't, stable trees have nothing to do with it as a normal user
would "hit" this when updating to run Linus's tree, just as easily as
they would "hit" it updating their stable kernel version.
thanks,
greg k-h
next prev parent reply other threads:[~2023-06-29 19:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 9:24 [PATCH] ASoC: qdsp6: q6apm: use dai link pcm id as pcm device number Srinivas Kandagatla
2023-06-29 15:43 ` Mark Brown
2023-06-29 16:06 ` Greg KH
2023-06-29 16:16 ` Mark Brown
2023-06-29 17:22 ` Greg KH
2023-06-29 17:38 ` Mark Brown
2023-06-29 18:48 ` Greg KH [this message]
2023-06-29 21:23 ` Mark Brown
2023-06-29 17:33 ` Srinivas Kandagatla
2023-06-29 17:42 ` Mark Brown
2023-06-30 5:42 ` Srinivas Kandagatla
2023-06-30 17:07 ` Mark Brown
2023-07-03 7:48 ` Johan Hovold
2023-07-03 8:03 ` Johan Hovold
2023-07-03 8:19 ` Takashi Iwai
2023-07-03 8:48 ` Johan Hovold
2023-07-03 12:21 ` Johan Hovold
2023-07-03 11:56 ` Mark Brown
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=2023062905-tiring-bauble-84ef@gregkh \
--to=greg@kroah.com \
--cc=Stable@vger.kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=johan+linaro@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=srinivas.kandagatla@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox