From: Mark Brown <broonie@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Venkata Prasad Potturu <venkataprasad.potturu@amd.com>,
Tom Rix <trix@redhat.com>,
Vijendar Mukunda <Vijendar.Mukunda@amd.com>,
Nick Desaulniers <ndesaulniers@google.com>,
alsa-devel@alsa-project.org, llvm@lists.linux.dev
Subject: Re: [PATCH] ASoC: amd: acp: Fix initialization of ext_intr_stat1 in i2s_irq_handler()
Date: Tue, 26 Jul 2022 14:07:45 +0100 [thread overview]
Message-ID: <165884086589.21705.8710449314865501400.b4-ty@kernel.org> (raw)
In-Reply-To: <20220725180539.1315066-1-nathan@kernel.org>
On Mon, 25 Jul 2022 11:05:39 -0700, Nathan Chancellor wrote:
> Clang warns:
>
> ../sound/soc/amd/acp/acp-platform.c:117:19: error: variable 'ext_intr_stat1' is uninitialized when used here [-Werror,-Wuninitialized]
> if (stream && (ext_intr_stat1 & stream->irq_bit)) {
> ^~~~~~~~~~~~~~
> ../sound/soc/amd/acp/acp-platform.c:97:35: note: initialize the variable 'ext_intr_stat1' to silence this warning
> u32 ext_intr_stat, ext_intr_stat1, i;
> ^
> = 0
> 1 error generated.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: amd: acp: Fix initialization of ext_intr_stat1 in i2s_irq_handler()
commit: d81677410f172c2b946393c09b46ff9e8dc1b6ec
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2022-07-26 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 18:05 Nathan Chancellor
2022-07-25 20:30 ` Tom Rix
2022-07-26 13:07 ` Mark Brown [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=165884086589.21705.8710449314865501400.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=Vijendar.Mukunda@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=trix@redhat.com \
--cc=venkataprasad.potturu@amd.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®