public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
To: Matt Flax <flatmax@flatmax.com>, Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	linux-next@vger.kernel.org, Nathan Chancellor <nathan@kernel.org>,
	clang-built-linux <llvm@lists.linux.dev>
Subject: build failure of next-20220822 due to 4e6bedd3c396 ("ASoC: codecs: add support for the TI SRC4392 codec")
Date: Mon, 22 Aug 2022 10:28:50 +0100	[thread overview]
Message-ID: <YwNMUlAmu/qCjuva@debian> (raw)

Hi All,

Not sure if it has been reported, builds of arm64 with clang failed to
build next-20220822 with the error:

sound/soc/codecs/src4xxx.c:280:3: error: variable 'd' is used uninitialized whenever switch default is taken [-Werror,-Wsometimes-uninitialized]
                default:
                ^~~~~~~
sound/soc/codecs/src4xxx.c:298:59: note: uninitialized use occurs here
                ret = regmap_write(src4xxx->regmap, SRC4XXX_RCV_PLL_11, d);
                                                                        ^
sound/soc/codecs/src4xxx.c:223:20: note: initialize the variable 'd' to silence this warning
        int val, pj, jd, d;
                          ^
                           = 0
sound/soc/codecs/src4xxx.c:280:3: error: variable 'jd' is used uninitialized whenever switch default is taken [-Werror,-Wsometimes-uninitialized]
                default:
                ^~~~~~~
sound/soc/codecs/src4xxx.c:293:59: note: uninitialized use occurs here
                ret = regmap_write(src4xxx->regmap, SRC4XXX_RCV_PLL_10, jd);
                                                                        ^~
sound/soc/codecs/src4xxx.c:223:17: note: initialize the variable 'jd' to silence this warning
        int val, pj, jd, d;
                       ^
                        = 0
sound/soc/codecs/src4xxx.c:280:3: error: variable 'pj' is used uninitialized whenever switch default is taken [-Werror,-Wsometimes-uninitialized]
                default:
                ^~~~~~~
sound/soc/codecs/src4xxx.c:288:59: note: uninitialized use occurs here
                ret = regmap_write(src4xxx->regmap, SRC4XXX_RCV_PLL_0F, pj);
                                                                        ^~
sound/soc/codecs/src4xxx.c:223:13: note: initialize the variable 'pj' to silence this warning
        int val, pj, jd, d;
                   ^
                    = 0
3 errors generated.

git bisect pointed to 4e6bedd3c396 ("ASoC: codecs: add support for the TI SRC4392 codec").

I will be happy to test any patch or provide any extra log if needed.


--
Regards
Sudip

             reply	other threads:[~2022-08-22  9:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22  9:28 Sudip Mukherjee (Codethink) [this message]
2022-08-22 16:34 ` build failure of next-20220822 due to 4e6bedd3c396 ("ASoC: codecs: add support for the TI SRC4392 codec") Nick Desaulniers

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=YwNMUlAmu/qCjuva@debian \
    --to=sudipm.mukherjee@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=flatmax@flatmax.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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