Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 29 Jun 2023 18:38:38 +0100
From:   Mark Brown <broonie@kernel.org>
To:     Greg KH <greg@kroah.com>
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
Message-ID: <1c1dd19e-cbc4-41fe-9e97-a07cfebdaa4b@sirena.org.uk>
References: <20230628092404.13927-1-srinivas.kandagatla@linaro.org>
 <c22fcc94-aa41-4ffd-bfe8-f0b9f15a76c0@sirena.org.uk>
 <2023062940-snore-brick-419b@gregkh>
 <9699a960-74b0-4064-b264-6cde06cd16fc@sirena.org.uk>
 <2023062958-thumping-ambulance-7a2f@gregkh>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="kJyOuHiyyBo6gZpK"
Content-Disposition: inline
In-Reply-To: <2023062958-thumping-ambulance-7a2f@gregkh>
Precedence: bulk


--kJyOuHiyyBo6gZpK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

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.

--kJyOuHiyyBo6gZpK
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmSdwZ0ACgkQJNaLcl1U
h9Ay1wf/V8UaFH7JxyAo2RN57WH5Ye9RCQpALdXWBo8riXGMcrU+5V3j2BOtv6j8
n7nOp3QM2HGoTbgFuSiUK+oNFilaNjNOzwB8I9VAG5Z3td0S9n4IEIsDPQkLFsm9
zt7I8TELzcKnbq0iQ/ob8Ubw3icGzVrPXCaWbkBcBCzyxsu3e9bkI33rhnymTyNE
ZN+BevBytonv53kKAoOekPt/Q48mRMSm/9yFDDerJTHC5+Ofj2eLmCepvkrCs0t6
vGfLDa07uKyZOmPblvStwNoPHh6swDc0264D2VzB4Vn8TnNiPtbMS59Bw2oK+9d2
VHUck3TXRnm57K1nTZSoTmP3WwaY+w==
=C4my
-----END PGP SIGNATURE-----

--kJyOuHiyyBo6gZpK--