From: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Srinivas Kandagatla <srini@kernel.org>,
Vinod Koul <vkoul@kernel.org>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
linux-sound@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soundwire: qcom: Use guard to avoid mixing cleanup and goto
Date: Mon, 1 Dec 2025 11:04:49 +0000 [thread overview]
Message-ID: <fba86e25-3327-4fbf-86f1-485bbaeec32d@oss.qualcomm.com> (raw)
In-Reply-To: <20251201102627.146182-2-krzysztof.kozlowski@oss.qualcomm.com>
On 12/1/25 10:26 AM, Krzysztof Kozlowski wrote:
> qcom_swrm_stream_alloc_ports() already uses cleanup.h but also has goto.
> Such combination is error-prone and discouraged:
>
> "... and that the "goto" statement can jump between scopes, the
> expectation is that usage of "goto" and cleanup helpers is never mixed
> in the same function."
>
> Actually simplify the code with a guard which allows to fix the
> discouraged style by removing the goto.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> ---
Thanks for the patch,
LGTM,
Reviewed-by: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
--srini> drivers/soundwire/qcom.c | 12 +++++-------
> 1 file changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/soundwire/qcom.c b/drivers/soundwire/qcom.c
> index 17afc5aa8b44..8102a1b0d516 100644
> --- a/drivers/soundwire/qcom.c
> +++ b/drivers/soundwire/qcom.c
> @@ -1228,7 +1228,7 @@ static int qcom_swrm_stream_alloc_ports(struct qcom_swrm_ctrl *ctrl,
> struct sdw_port_runtime *p_rt;
> struct sdw_slave *slave;
> unsigned long *port_mask;
> - int maxport, pn, nports = 0, ret = 0;
> + int maxport, pn, nports = 0;
> unsigned int m_port;
> struct sdw_port_config *pconfig __free(kfree) = kcalloc(ctrl->nports,
> sizeof(*pconfig), GFP_KERNEL);
> @@ -1246,7 +1246,8 @@ static int qcom_swrm_stream_alloc_ports(struct qcom_swrm_ctrl *ctrl,
> sconfig.type = stream->type;
> sconfig.bps = 1;
>
> - mutex_lock(&ctrl->port_lock);
> + guard(mutex)(&ctrl->port_lock);
> +
> list_for_each_entry(m_rt, &stream->master_list, stream_node) {
> /*
> * For streams with multiple masters:
> @@ -1272,8 +1273,7 @@ static int qcom_swrm_stream_alloc_ports(struct qcom_swrm_ctrl *ctrl,
>
> if (pn > maxport) {
> dev_err(ctrl->dev, "All ports busy\n");
> - ret = -EBUSY;
> - goto out;
> + return -EBUSY;
> }
> set_bit(pn, port_mask);
> pconfig[nports].num = pn;
> @@ -1285,10 +1285,8 @@ static int qcom_swrm_stream_alloc_ports(struct qcom_swrm_ctrl *ctrl,
>
> sdw_stream_add_master(&ctrl->bus, &sconfig, pconfig,
> nports, stream);
> -out:
> - mutex_unlock(&ctrl->port_lock);
>
> - return ret;
> + return 0;
> }
>
> static int qcom_swrm_hw_params(struct snd_pcm_substream *substream,
next prev parent reply other threads:[~2025-12-01 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 10:26 [PATCH] soundwire: qcom: Use guard to avoid mixing cleanup and goto Krzysztof Kozlowski
2025-12-01 10:59 ` Konrad Dybcio
2025-12-01 11:04 ` Srinivas Kandagatla [this message]
2025-12-16 9:19 ` Vinod Koul
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=fba86e25-3327-4fbf-86f1-485bbaeec32d@oss.qualcomm.com \
--to=srinivas.kandagatla@oss.qualcomm.com \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=pierre-louis.bossart@linux.dev \
--cc=srini@kernel.org \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.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