linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Herve Codina <herve.codina@bootlin.com>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: broonie@kernel.org, leoyang.li@nxp.com,
	linuxppc-dev@lists.ozlabs.org, qiang.zhao@nxp.com
Subject: Re: [PATCH] soc: fsl: cpm1: qmc: fix error return code in qmc_probe()
Date: Tue, 28 Nov 2023 14:21:58 +0100	[thread overview]
Message-ID: <20231128142158.302eb348@bootlin.com> (raw)
In-Reply-To: <20231128130942.2457873-1-yangyingliang@huawei.com>

Hi Yang,

On Tue, 28 Nov 2023 21:09:42 +0800
Yang Yingliang <yangyingliang@huawei.com> wrote:

> If platform_get_irq() fails, it need return error code in
> qmc_probe().
> 
> Fixes: 3178d58e0b97 ("soc: fsl: cpm1: Add support for QMC")
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> ---
>  drivers/soc/fsl/qe/qmc.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/soc/fsl/qe/qmc.c b/drivers/soc/fsl/qe/qmc.c
> index 92ec76c03965..65109f279a6b 100644
> --- a/drivers/soc/fsl/qe/qmc.c
> +++ b/drivers/soc/fsl/qe/qmc.c
> @@ -1386,8 +1386,10 @@ static int qmc_probe(struct platform_device *pdev)
>  	qmc_write16(qmc->scc_regs + SCC_SCCM, 0x0000);
>  	qmc_write16(qmc->scc_regs + SCC_SCCE, 0x000F);
>  	irq = platform_get_irq(pdev, 0);
> -	if (irq < 0)
> +	if (irq < 0) {
> +		ret = irq;
>  		goto err_tsa_serial_disconnect;
> +	}
>  	ret = devm_request_irq(qmc->dev, irq, qmc_irq_handler, 0, "qmc", qmc);
>  	if (ret < 0)
>  		goto err_tsa_serial_disconnect;

Thanks for this patch.

Acked-by: Herve Codina <herve.codina@bootlin.com>

Best regards,
Hervé

      reply	other threads:[~2023-11-28 13:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 13:09 [PATCH] soc: fsl: cpm1: qmc: fix error return code in qmc_probe() Yang Yingliang
2023-11-28 13:21 ` Herve Codina [this message]

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=20231128142158.302eb348@bootlin.com \
    --to=herve.codina@bootlin.com \
    --cc=broonie@kernel.org \
    --cc=leoyang.li@nxp.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=qiang.zhao@nxp.com \
    --cc=yangyingliang@huawei.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;
as well as URLs for NNTP newsgroup(s).