From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 02E26EB64D9 for ; Thu, 29 Jun 2023 19:00:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232375AbjF2TAu (ORCPT ); Thu, 29 Jun 2023 15:00:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36708 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232647AbjF2TAt (ORCPT ); Thu, 29 Jun 2023 15:00:49 -0400 Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C59A11B1; Thu, 29 Jun 2023 12:00:47 -0700 (PDT) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id DDF1D32009BB; Thu, 29 Jun 2023 15:00:42 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 29 Jun 2023 15:00:44 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm2; t=1688065242; x=1688151642; bh=bp 7/jbgKluLBqcOde9/5kTokHhE3IOxuA/FlerD3+9Q=; b=i2bOVJJamStYbA3zgv YU+tzEwjLLEXriTCJYN0Hj/d5N8xMer+YwSGpVxKyXg9oRC5edjxci2DiTu3XZvc YhV9F9gSo2vb/M9WrAS3GmZoldmdysGri28JhWJ5k4Y7wJPFIAq3L7zTsPEwIecV KHf6F2ETgsSdI/6+b0uCuasrWwbesrqCcEdW2iDU8n8tQGgjYcrshlo0gP84Acru W1/BlgbjlPqBmplCNDTkb+Sv2mp5Q38N/JUNphllqbtYzVTvSl9+ITLsbMf6znK1 132VWYTkrf8Vq6gdcg7tEIN745I6ZEXnNneTSGMK1q0O6Sc3iYwUTYL+4GQN2nkq DB7w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; t=1688065242; x=1688151642; bh=bp7/jbgKluLBq cOde9/5kTokHhE3IOxuA/FlerD3+9Q=; b=bku9wo46OJ5u7zQmcZi3bXLF1vMpa /MVERS59KH6yH6rCfeyxyFeZzNq+NlDFxMG9iZ9ttGyuw7aaYH7NvAhMJ0r96/Dj wA1BLDI/wU2bXWGiQUmYoA5MXzRuEg7h8Zuy/F3AaIk58iWHzrFyFBs1a/dHX48v O1+5KUuFcZdNqcR63ux2+rVLWDsSwYUaEN8mBZZWquZCqF3FkabVHo7We3Ir34fI CR3m05RYvLwzskqbXnd+J6nU3Q3wEejWOCN3vgTO5GrT4iJXCuu88qvxuGFPbQg0 j3DsHWKQo4Lc+issk9ZkZfaVXgwxS8M3h2phqh0i+cpAZz6vkQxYLYqsw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrtdeggddufeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepifhrvghg ucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecuggftrfgrthhtvghrnhepheegvd evvdeljeeugfdtudduhfekledtiefhveejkeejuefhtdeufefhgfehkeetnecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorg hhrdgtohhm X-ME-Proxy: Feedback-ID: i787e41f1:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 29 Jun 2023 15:00:40 -0400 (EDT) Date: Thu, 29 Jun 2023 20:48:42 +0200 From: Greg KH To: Mark Brown Cc: Srinivas Kandagatla , 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: <2023062905-tiring-bauble-84ef@gregkh> References: <20230628092404.13927-1-srinivas.kandagatla@linaro.org> <2023062940-snore-brick-419b@gregkh> <9699a960-74b0-4064-b264-6cde06cd16fc@sirena.org.uk> <2023062958-thumping-ambulance-7a2f@gregkh> <1c1dd19e-cbc4-41fe-9e97-a07cfebdaa4b@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1c1dd19e-cbc4-41fe-9e97-a07cfebdaa4b@sirena.org.uk> Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org 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