[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9699a960-74b0-4064-b264-6cde06cd16fc@sirena.org.uk>
Date: Thu, 29 Jun 2023 17:16:44 +0100
From: Mark Brown <broonie@...nel.org>
To: Greg KH <greg@...ah.com>
Cc: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
johan+linaro@...nel.org, perex@...ex.cz, tiwai@...e.com,
lgirdwood@...il.com, ckeepax@...nsource.cirrus.com,
kuninori.morimoto.gx@...esas.com, linux-kernel@...r.kernel.org,
pierre-louis.bossart@...ux.intel.com, alsa-devel@...a-project.org,
Stable@...r.kernel.org
Subject: Re: [PATCH] ASoC: qdsp6: q6apm: use dai link pcm id as pcm device
number
On Thu, Jun 29, 2023 at 06:06:05PM +0200, Greg KH wrote:
> On Thu, Jun 29, 2023 at 04:43:57PM +0100, Mark Brown wrote:
> > Won't this be an ABI change? That seems like it'd disrupt things in
> > stable.
> ABI changes should disrupt things just the same in Linus's tree, why is
> stable any different?
This is a numbering resulting from enumeration thing so it gets to be
like the issues we've had with the order in which block and ethernet
devices appear, it's on the edge the extent to which people might be
relying on it. If it's causing some problem as is and there's a reason
to do something (see the first half of my reply...) but the case gets
even harder to make with stable.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists