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 18:06:05 +0200 [thread overview]
Message-ID: <2023062940-snore-brick-419b@gregkh> (raw)
In-Reply-To: <c22fcc94-aa41-4ffd-bfe8-f0b9f15a76c0@sirena.org.uk>
On Thu, Jun 29, 2023 at 04:43:57PM +0100, Mark Brown wrote:
> On Wed, Jun 28, 2023 at 10:24:04AM +0100, Srinivas Kandagatla wrote:
> > For some reason we ended up with a setup without this flag.
> > This resulted in inconsistent sound card devices numbers which
> > are also not starting as expected at dai_link->id.
> > (Ex: MultiMedia1 pcm ended up with device number 4 instead of 0)
>
> Why is this a problem?
>
> > With this patch patch now the MultiMedia1 PCM ends up with device number 0
> > as expected.
> >
> > Fixes: 9b4fe0f1cd79 ("ASoC: qdsp6: audioreach: add q6apm-dai support")
> > Cc: <Stable@vger.kernel.org>
>
> 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?
thanks,
greg k-h
next prev parent reply other threads:[~2023-06-29 16:06 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 [this message]
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
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=2023062940-snore-brick-419b@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