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 26FEEC7EE23 for ; Wed, 17 May 2023 16:50:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229483AbjEQQt4 (ORCPT ); Wed, 17 May 2023 12:49:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40104 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229590AbjEQQtz (ORCPT ); Wed, 17 May 2023 12:49:55 -0400 Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2A44C40F7; Wed, 17 May 2023 09:49:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1684342194; x=1715878194; h=message-id:date:mime-version:subject:to:references:from: in-reply-to:content-transfer-encoding; bh=KS6uI5RGH1xHM6b9lrfHL7GS8cXP0VR3O3NP1UIgCzg=; b=ElDpZ8m5ZhWd1fHcItYB0+FjwnZwffR94s8GzMUmzOUHXEEgTDUcJQIP i1x7c3Yt//AxZK8r/Q9Pwys5UWJ38QTZLIp7yzeDpEom8yItn/pG5AA8I HsiKougpklrSuYRJddBXjS3+oQkDZvd/yOh7TVCoDAJ9idm+0k8CT3DiJ CFqyxZDAQ3VlLBK9eDoJ0OZlxeKFgCvcYlKAwlVPoraA7waGII7v4Lf0H phcyGApiVd+THB9n2CtpsYFkp0pQxshp2U2eg1touZYAj9dv4nWzZIteD LK02f5ndp6xNVZG7M3+vjekbwJCIZREyHrmdpi6RQJItdw50RBjEq9Jn/ g==; X-IronPort-AV: E=McAfee;i="6600,9927,10713"; a="350649321" X-IronPort-AV: E=Sophos;i="5.99,282,1677571200"; d="scan'208";a="350649321" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 May 2023 09:48:48 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10713"; a="734764313" X-IronPort-AV: E=Sophos;i="5.99,282,1677571200"; d="scan'208";a="734764313" Received: from pgopdahl-mobl1.amr.corp.intel.com (HELO [10.209.16.196]) ([10.209.16.196]) by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 May 2023 09:48:47 -0700 Message-ID: <7638419f-7df1-a31a-e68e-1c315f57cabf@linux.intel.com> Date: Wed, 17 May 2023 11:45:09 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Thunderbird/102.10.0 Subject: Re: [PATCH] soundwire: qcom: add proper error paths in qcom_swrm_startup() Content-Language: en-US To: Krzysztof Kozlowski , Andy Gross , Bjorn Andersson , Konrad Dybcio , Vinod Koul , Bard Liao , Sanyog Kale , linux-arm-msm@vger.kernel.org, alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org References: <20230517163736.997553-1-krzysztof.kozlowski@linaro.org> From: Pierre-Louis Bossart In-Reply-To: <20230517163736.997553-1-krzysztof.kozlowski@linaro.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/17/23 11:37, Krzysztof Kozlowski wrote: > Reverse actions in qcom_swrm_startup() error paths to avoid leaking > stream memory and keeping runtime PM unbalanced. > > Signed-off-by: Krzysztof Kozlowski Reviewed-by: Pierre-Louis Bossart