From: Dan Carpenter <error27@gmail.com>
To: Trevor Wu <trevor.wu@mediatek.com>
Cc: broonie@kernel.org, lgirdwood@gmail.com, tiwai@suse.com,
perex@perex.cz, matthias.bgg@gmail.com,
alsa-devel@alsa-project.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: mediatek: mt8188: remove etdm dead code
Date: Thu, 2 Feb 2023 15:17:04 +0300 [thread overview]
Message-ID: <Y9upwNAzXzSxmiFo@kadam> (raw)
In-Reply-To: <20230202103704.15626-1-trevor.wu@mediatek.com>
On Thu, Feb 02, 2023 at 06:37:04PM +0800, Trevor Wu wrote:
> Some Smatch static checker warning like below was found.
>
> sound/soc/mediatek/mt8188/mt8188-dai-etdm.c:2487
> mt8188_dai_etdm_parse_of()
> warn: 'ret' returned from snprintf() might be larger than 48
>
> 2479 for (i = 0; i < MT8188_AFE_IO_ETDM_NUM; i++) {
> 2480 dai_id = ETDM_TO_DAI_ID(i);
> 2481 etdm_data = afe_priv->dai_priv[dai_id];
> 2482
> 2483 ret = snprintf(prop, sizeof(prop),
> 2484 "mediatek,%s-multi-pin-mode",
> 2485 of_afe_etdms[i].name);
> 2486 if (ret < 0) {
> --> 2487 dev_err(afe->dev, "%s snprintf
> err=%d\n",
> 2488
>
> In linux kernel, snprintf() never returns negatives. On the other hand,
> the format string like "mediatek,%s-multi-pin-mode" must be smaller
> than sizeof(prop)=48.
>
> After discussing in the mail thread[1], I remove the dead code to fix
> the Smatch warnings.
>
> [1]: https://lore.kernel.org/all/Y9EdBg641tJDDrt%2F@kili/
>
> Signed-off-by: Trevor Wu <trevor.wu@mediatek.com>
> ---
Thanks!
Regards,
dan carpenter
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-02-02 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 10:37 [PATCH] ASoC: mediatek: mt8188: remove etdm dead code Trevor Wu
2023-02-02 12:17 ` Dan Carpenter [this message]
2023-02-03 14:56 ` Mark Brown
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=Y9upwNAzXzSxmiFo@kadam \
--to=error27@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=trevor.wu@mediatek.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