linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org, Lee Jones <lee@kernel.org>,
	Pavel Machek <pavel@kernel.org>,
	linux-leds@vger.kernel.org,
	Stefan Kalscheuer <stefan@stklcode.de>
Subject: Re: Apply ccc35ff2fd2911986b716a87fe65e03fac2312c9 to 5.15, 6.1, and 6.6
Date: Sat, 6 Dec 2025 19:37:43 -0500	[thread overview]
Message-ID: <aTTMV34MPzGJc6TK@laps> (raw)
In-Reply-To: <20251204000025.GA468348@ax162>

On Wed, Dec 03, 2025 at 05:00:25PM -0700, Nathan Chancellor wrote:
>Hi stable folks,
>
>Please apply commit ccc35ff2fd29 ("leds: spi-byte: Use
>devm_led_classdev_register_ext()") to 5.15, 6.1, and 6.6. It
>inadvertently addresses an instance of -Wuninitialized visible with
>clang-21 and newer:
>
>  drivers/leds/leds-spi-byte.c:99:26: error: variable 'child' is uninitialized when used here [-Werror,-Wuninitialized]
>     99 |         of_property_read_string(child, "label", &name);
>        |                                 ^~~~~
>  drivers/leds/leds-spi-byte.c:83:27: note: initialize the variable 'child' to silence this warning
>     83 |         struct device_node *child;
>        |                                  ^
>        |                                   = NULL
>
>It applies cleanly to 6.6. I have attached a backport for 6.1 and 5.15,
>which can be generated locally with:
>
>  $ git format-patch -1 --stdout ccc35ff2fd2911986b716a87fe65e03fac2312c9 | sed 's;strscpy;strlcpy;' | patch -p1

Queued up. I just picked up the dependency instead of changing the patch.

-- 
Thanks,
Sasha

      reply	other threads:[~2025-12-07  0:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04  0:00 Apply ccc35ff2fd2911986b716a87fe65e03fac2312c9 to 5.15, 6.1, and 6.6 Nathan Chancellor
2025-12-07  0:37 ` Sasha Levin [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=aTTMV34MPzGJc6TK@laps \
    --to=sashal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=lee@kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=pavel@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=stefan@stklcode.de \
    /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).