From: Mark Brown <broonie@kernel.org>
To: Suraj Sonawane <surajsonawane0215@gmail.com>
Cc: lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
linux-sound@vger.kernel.org, perex@perex.cz, tiwai@suse.com
Subject: Re: [PATCH v2] sound: fix uninit-value in i2s_dma_isr
Date: Mon, 4 Nov 2024 12:41:44 +0000 [thread overview]
Message-ID: <d1710182-b4e0-4bb9-bebf-1fa7c48c77fd@sirena.org.uk> (raw)
In-Reply-To: <20241102123630.25446-1-surajsonawane0215@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
On Sat, Nov 02, 2024 at 06:06:30PM +0530, Suraj Sonawane wrote:
> Fix an issue detected by the Smatch tool:
>
> sound/soc/bcm/bcm63xx-pcm-whistler.c:264 i2s_dma_isr()
> error: uninitialized symbol 'val_1'.
> sound/soc/bcm/bcm63xx-pcm-whistler.c:264 i2s_dma_isr()
> error: uninitialized symbol 'val_2'.
Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.
Please don't send new patches in reply to old patches or serieses, this
makes it harder for both people and tools to understand what is going
on - it can bury things in mailboxes and make it difficult to keep track
of what current patches are, both for the new patches and the old ones.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-11-04 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 17:08 [PATCH] " Suraj Sonawane
2024-10-30 17:14 ` Mark Brown
2024-10-31 6:47 ` Suraj Sonawane
2024-10-31 16:17 ` Mark Brown
2024-11-01 9:02 ` Suraj Sonawane
2024-11-01 13:15 ` Mark Brown
2024-11-02 12:40 ` Suraj Sonawane
2024-11-02 12:36 ` [PATCH v2] " Suraj Sonawane
2024-11-04 12:41 ` Mark Brown [this message]
2024-11-05 11:03 ` Suraj Sonawane
2024-11-05 16:38 ` Mark Brown
2024-11-06 8:24 ` Suraj Sonawane
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=d1710182-b4e0-4bb9-bebf-1fa7c48c77fd@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=surajsonawane0215@gmail.com \
--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
all inboxes | Powered by JetHome®