From: Suraj Sonawane <surajsonawane0215@gmail.com>
To: Lee Jones <lee@kernel.org>, pavel@ucw.cz
Cc: matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: (subset) [PATCH] leds: Fix uninitialized variable 'ret' in mt6370_mc_pattern_clear
Date: Fri, 11 Oct 2024 18:52:18 +0530 [thread overview]
Message-ID: <7274be28-aefe-49b1-b8e1-dd1c2bad96d0@gmail.com> (raw)
In-Reply-To: <172863776565.3130628.18378710932238203204.b4-ty@kernel.org>
On 11/10/24 14:39, Lee Jones wrote:
> On Sun, 06 Oct 2024 18:43:37 +0530, SurajSonawane2415 wrote:
>> Fix the uninitialized symbol 'ret' in the function mt6370_mc_pattern_clear
>> to resolve the following warning:
>> drivers/leds/rgb/leds-mt6370-rgb.c:604 mt6370_mc_pattern_clear()
>> error: uninitialized symbol 'ret'.
>> Initialize 'ret' to 0 to prevent undefined behavior from uninitialized
>> access.
>>
>> [...]
>
> Applied, thanks!
>
> [1/1] leds: Fix uninitialized variable 'ret' in mt6370_mc_pattern_clear
> commit: b5a5659aebfffbcddb81abafe042fb4044b6ff9e
>
> --
> Lee Jones [李琼斯]
>
Thank you! I'm glad the patch was applied. I'll ensure future patches
follow the necessary guidelines.
Best regards,
Suraj Sonawane
next prev parent reply other threads:[~2024-10-11 13:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-06 13:13 [PATCH] leds: Fix uninitialized variable 'ret' in mt6370_mc_pattern_clear SurajSonawane2415
2024-10-11 7:47 ` Lee Jones
2024-10-11 13:20 ` Suraj Sonawane
2024-10-11 9:09 ` (subset) " Lee Jones
2024-10-11 13:22 ` Suraj Sonawane [this message]
2024-10-15 8:58 ` Lee Jones
2024-10-16 4:21 ` [PATCH v2] " Suraj Sonawane
2024-10-16 7:53 ` (subset) " Lee Jones
2024-10-16 12:13 ` Suraj Sonawane
2024-10-16 4:25 ` (subset) [PATCH] " 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=7274be28-aefe-49b1-b8e1-dd1c2bad96d0@gmail.com \
--to=surajsonawane0215@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=pavel@ucw.cz \
/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;
as well as URLs for NNTP newsgroup(s).