[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f9fa484f-b7fb-4a32-9958-be41ed67504c@gmail.com>
Date: Tue, 5 Nov 2024 16:33:54 +0530
From: Suraj Sonawane <surajsonawane0215@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: lgirdwood@...il.com, linux-kernel@...r.kernel.org,
linux-sound@...r.kernel.org, perex@...ex.cz, tiwai@...e.com
Subject: Re: [PATCH v2] sound: fix uninit-value in i2s_dma_isr
On 04/11/24 18:11, Mark Brown wrote:
> 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.
Thank you for the guidance. I understand the importance of following the
existing format for subject lines to maintain consistency within the
subsystem. When I submitted the v2 patch earlier, I had been considering
this, but I mistakenly thought that switching subject lines between v1
and v2 wasn’t necessary. Moving forward, I'll make sure my patches align
with the the style for the subsystem and will submit them as new threads
to avoid confusion.
Thank you again for your feedback.
Powered by blists - more mailing lists