From: Shengjiu Wang <shengjiu.wang@gmail.com>
To: Pieterjan Camerlynck <pieterjan.camerlynck@gmail.com>
Cc: alsa-devel@alsa-project.org,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Xiubo Li <Xiubo.Lee@gmail.com>
Subject: Re: [PATCH] ASoC: fsl_sai: fix incorrect mclk number in error message
Date: Sun, 8 May 2022 15:58:35 +0800 [thread overview]
Message-ID: <CAA+D8APkCt4N9_Gm8324ffR-vAvX5e6eq7tegMy-MLMy4zRZVQ@mail.gmail.com> (raw)
In-Reply-To: <20220507123101.10938-1-pieterjan.camerlynck@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]
On Sat, May 7, 2022 at 8:31 PM Pieterjan Camerlynck <
pieterjan.camerlynck@gmail.com> wrote:
> In commit <c3ecef21c3f26> ("ASoC: fsl_sai: add sai master mode support")
> the loop was changed to start iterating from 1 instead of 0. The error
> message however was not updated, reporting the wrong clock to the user.
>
> Signed-off-by: Pieterjan Camerlynck <pieterjan.camerlynck@gmail.com>
>
Acked-by: Shengjiu Wang <shengjiu.wang@gmail.com>
Best Regards
Wang Shengjiu
> ---
> sound/soc/fsl/fsl_sai.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/soc/fsl/fsl_sai.c b/sound/soc/fsl/fsl_sai.c
> index ffc24afb5a7a..f0602077b385 100644
> --- a/sound/soc/fsl/fsl_sai.c
> +++ b/sound/soc/fsl/fsl_sai.c
> @@ -1054,7 +1054,7 @@ static int fsl_sai_probe(struct platform_device
> *pdev)
> sai->mclk_clk[i] = devm_clk_get(&pdev->dev, tmp);
> if (IS_ERR(sai->mclk_clk[i])) {
> dev_err(&pdev->dev, "failed to get mclk%d clock:
> %ld\n",
> - i + 1, PTR_ERR(sai->mclk_clk[i]));
> + i, PTR_ERR(sai->mclk_clk[i]));
> sai->mclk_clk[i] = NULL;
> }
> }
> --
> 2.25.1
>
>
[-- Attachment #2: Type: text/html, Size: 2122 bytes --]
next prev parent reply other threads:[~2022-05-09 1:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 12:31 [PATCH] ASoC: fsl_sai: fix incorrect mclk number in error message Pieterjan Camerlynck
2022-05-08 7:58 ` Shengjiu Wang [this message]
2022-08-05 3:07 ` Shengjiu Wang
-- strict thread matches above, loose matches on Subject: below --
2022-08-05 6:39 Pieterjan Camerlynck
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=CAA+D8APkCt4N9_Gm8324ffR-vAvX5e6eq7tegMy-MLMy4zRZVQ@mail.gmail.com \
--to=shengjiu.wang@gmail.com \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=pieterjan.camerlynck@gmail.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).