From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Vijendar Mukunda <Vijendar.Mukunda@amd.com>,
broonie@kernel.org, alsa-devel@alsa-project.org
Cc: amadeuszx.slawinski@linux.intel.com,
Basavaraj.Hiregoudar@amd.com, Sunil-kumar.Dommati@amd.com,
zhuning@everest-semi.com, kernel test robot <lkp@intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] ASoC: amd: fix for variable set but not used warning
Date: Sat, 9 Jul 2022 09:33:57 +0200 [thread overview]
Message-ID: <e2eab942-f122-7e37-e3a3-c8a1e153c91b@wanadoo.fr> (raw)
In-Reply-To: <20220707132613.3150931-3-Vijendar.Mukunda@amd.com>
Le 07/07/2022 à 15:26, Vijendar Mukunda a écrit :
> Fix below kernel warning.
>>>> sound/soc/amd/acp-es8336.c:200:13: warning: variable 'ret' set but
>>>> not used [-Wunused-but-set-variable]
>
Hi,
this patch, looks odd to me.
> Signed-off-by: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
> Reported-by: kernel test robot <lkp@intel.com>
> ---
> sound/soc/amd/acp-es8336.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/sound/soc/amd/acp-es8336.c b/sound/soc/amd/acp-es8336.c
> index 90f4e5809c72..e1479ae684e9 100644
> --- a/sound/soc/amd/acp-es8336.c
> +++ b/sound/soc/amd/acp-es8336.c
> @@ -206,6 +206,8 @@ static int st_es8336_late_probe(struct snd_soc_card *card)
> dev_err(card->dev, "can not find codec dev\n");
The next devm_acpi_dev_add_driver_gpios() will fail, should we return
immediately?
>
> ret = devm_acpi_dev_add_driver_gpios(codec_dev, acpi_es8336_gpios);
> + if (ret)
> + dev_warn(card->dev, "Failed to add driver gpios\n");
Should we return immediately?
>
> gpio_pa = gpiod_get_optional(codec_dev, "pa-enable", GPIOD_OUT_LOW);
> if (IS_ERR(gpio_pa)) {
> @@ -213,6 +215,7 @@ static int st_es8336_late_probe(struct snd_soc_card *card)
> "could not get pa-enable GPIO\n");
> gpiod_put(gpio_pa);
> put_device(codec_dev);
> + return ret;
Here, we return 'ret' which is what is returned by
devm_acpi_dev_add_driver_gpios(). So there doesn't seem to be a link
with this block which checks for gpiod_get_optional() errors.
Moreover, returning an error for something that is optional
(gpiod_get_optional()) looks strange.
Finally, should an error be returned, maybe PTR_ERR(gpio_pa) would be
better here.
Just my 2c.
CJ
> }
> return 0;
> }
next prev parent reply other threads:[~2022-07-09 7:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 13:26 [PATCH 1/3] ASoC: amd: remove unused header file inclusion Vijendar Mukunda
2022-07-07 13:26 ` [PATCH 2/3] ASoC: amd: drop machine driver remove function Vijendar Mukunda
2022-07-07 13:26 ` [PATCH 3/3] ASoC: amd: fix for variable set but not used warning Vijendar Mukunda
2022-07-09 7:33 ` Christophe JAILLET [this message]
2022-07-09 11:12 ` Mukunda,Vijendar
2022-07-11 2:59 ` Zhu Ning
2022-07-08 20:47 ` [PATCH 1/3] ASoC: amd: remove unused header file inclusion 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=e2eab942-f122-7e37-e3a3-c8a1e153c91b@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=zhuning@everest-semi.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
all inboxes | Powered by JetHome®