From: Lee Jones <lee@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Marek Beh'un <kabel@kernel.org>, Pavel Machek <pavel@ucw.cz>,
linux-leds@vger.kernel.org
Subject: Re: [PATCH] leds: Fix BUG_ON check for LED_COLOR_ID_MULTI that is always false
Date: Fri, 6 Oct 2023 15:45:18 +0100 [thread overview]
Message-ID: <20231006144518.GD808963@google.com> (raw)
In-Reply-To: <ZSAcKoRFop-NCsFG@FVFF77S0Q05N.cambridge.arm.com>
On Fri, 06 Oct 2023, Mark Rutland wrote:
> On Fri, Oct 06, 2023 at 03:24:04PM +0100, Mark Rutland wrote:
> > On Tue, Aug 01, 2023 at 05:16:23PM +0200, Marek Beh'un wrote:
> > > At the time we call
> > > BUG_ON(props.color == LED_COLOR_ID_MULTI);
> > > the props variable is still initialized to zero.
> > >
> > > Call the BUG_ON only after we parse fwnode into props.
> > >
> > > Fixes: 77dce3a22e89 ("leds: disallow /sys/class/leds/*:multi:* for now")
> > > Signed-off-by: Marek Beh'un <kabel@kernel.org>
> >
> > I've just discovered this has broken boot on my Libre Computer
> > AML-A311D-CC-V0.2, which was working just fine with Debian 12's stock kernel:
>
> Sorry the the noise; I've just spotted this is fixed by:
>
> https://lore.kernel.org/linux-leds/20230918140724.18634-1-kabel@kernel.org/
>
> ... and I look forward to that hitting mainline :)
Your long agonising wait is over:
commit 9dc1664fab2246bc2c3e9bf2cf21518a857f9b5b
Author: Marek Behún <kabel@kernel.org>
Date: Mon Sep 18 16:07:24 2023 +0200
leds: Drop BUG_ON check for LED_COLOR_ID_MULTI
Commit c3f853184bed ("leds: Fix BUG_ON check for LED_COLOR_ID_MULTI that
is always false") fixed a no-op BUG_ON. This turned out to cause a
regression, since some in-tree device-tree files already use
LED_COLOR_ID_MULTI.
Drop the BUG_ON altogether.
Fixes: c3f853184bed ("leds: Fix BUG_ON check for LED_COLOR_ID_MULTI that is always false")
Reported-by: Da Xue <da@libre.computer>
Closes: https://lore.kernel.org/linux-leds/ZQLelWcNjjp2xndY@duo.ucw.cz/T/
Signed-off-by: Marek Behún <kabel@kernel.org>
Link: https://lore.kernel.org/r/20230918140724.18634-1-kabel@kernel.org
Signed-off-by: Lee Jones <lee@kernel.org>
---
drivers/leds/led-core.c | 4 ----
1 file changed, 4 deletions(-)
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-10-06 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 15:16 [PATCH] leds: Fix BUG_ON check for LED_COLOR_ID_MULTI that is always false Marek Behún
2023-08-17 10:26 ` (subset) " Lee Jones
2023-10-06 14:24 ` Mark Rutland
2023-10-06 14:39 ` Mark Rutland
2023-10-06 14:45 ` Lee Jones [this message]
2023-10-06 15:11 ` Mark Rutland
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=20231006144518.GD808963@google.com \
--to=lee@kernel.org \
--cc=kabel@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.