From: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>
To: YueHaibing <yuehaibing@huawei.com>,
lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com, tangmeng@uniontech.com
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH -next] ASoC: amd: acp: signedness bug in acp-renoir
Date: Sat, 5 Mar 2022 20:19:39 +0530 [thread overview]
Message-ID: <9dcc09ec-a796-b52a-779a-52d4c388fa27@amd.com> (raw)
In-Reply-To: <20220305123519.26788-1-yuehaibing@huawei.com>
This error handling already fixed by Dan here
https://patchwork.kernel.org/project/alsa-devel/patch/20220304131449.GC28739@kili/
On 3/5/2022 6:05 PM, YueHaibing wrote:
> [CAUTION: External Email]
>
> In renoir_audio_probe() platform_get_irq_byname() may return error,
> but i2s_irq now is unsigned int so the error handling is never triggered.
>
> Fixes: 3304a242f45a ("ASoC: amd: Use platform_get_irq_byname() to get the interrupt")
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
> sound/soc/amd/acp/amd.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/soc/amd/acp/amd.h b/sound/soc/amd/acp/amd.h
> index 8fd38bf4d3bd..acb50d9fca58 100644
> --- a/sound/soc/amd/acp/amd.h
> +++ b/sound/soc/amd/acp/amd.h
> @@ -96,7 +96,7 @@ struct acp_dev_data {
> char *name;
> struct device *dev;
> void __iomem *acp_base;
> - unsigned int i2s_irq;
> + int i2s_irq;
>
> /* SOC specific dais */
> struct snd_soc_dai_driver *dai_driver;
> --
> 2.17.1
>
prev parent reply other threads:[~2022-03-05 14:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 12:35 [PATCH -next] ASoC: amd: acp: signedness bug in acp-renoir YueHaibing
2022-03-05 14:49 ` Ajit Kumar Pandey [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=9dcc09ec-a796-b52a-779a-52d4c388fa27@amd.com \
--to=ajitkumar.pandey@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tangmeng@uniontech.com \
--cc=tiwai@suse.com \
--cc=yuehaibing@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