From: Pavel Machek <pavel@ucw.cz>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Matthias Schiffer <mschiffer@universe-factory.net>,
Sasha Levin <Alexander.Levin@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Matthieu CASTET <matthieu.castet@parrot.com>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>
Subject: Re: [PATCH AUTOSEL for 4.14 065/110] led: core: Fix brightness setting when setting delay_off=0
Date: Tue, 13 Mar 2018 14:27:48 +0100 [thread overview]
Message-ID: <20180313132748.GA20246@amd> (raw)
In-Reply-To: <20180313093703.GB27669@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 2201 bytes --]
Hi!
> > > At least 7b6af2c531 ("leds: core: Fix regression caused by commit
> > > 2b83ff96f51d") is missing, causing visible regressions (LEDs not working at
> > > all) on some OpenWrt devices. This was fixed in 4.4.121 by reverting the
> > > offending commit, but if I followed the discussion correctly, 4.9 should
> > > get the follow-up commit 7b6af2c531 instead (like 4.14 already did).
> > >
> > > Jacek's mail I replied to mentions that eb1610b4c273 ("led: core: Fix
> > > blink_brightness setting race") should be included in 4.9 as well, but I
> > > don't know the impact of the issue it fixes.
> >
> > It doesn't fix any reported issue, but is just an improvement
> > aiming at preventing potential races while changing blink brightness.
> >
> > After taking closer look it turns out that for the patches in question
> > to apply cleanly we need in 4.9 also a patch which introduces atomic
> > bit fields for blink flags.
> >
> > Effectively, here is the list of patches required in 4.9 stable:
> >
> > Revert "led: core: Fix brightness setting when setting delay_off=0"
> >
> > followed by:
> >
> > a9c6ce57ec ("led: core: Use atomic bit-field for the blink-flags")
> > eb1610b4c2 ("led: core: Fix blink_brightness setting race")
> > 2b83ff96f5 ("led: core: Fix brightness setting when setting delay_off=0")
> > 7b6af2c531 ("leds: core: Fix regression caused by commit 2b83ff96f51d")
>
> Odd, I just got another report that the 4.9.87 release fixed some
> reported LED issues, so why do I need all of these?
>
> Should I just revert the single 2b83ff96f51d commit here instead?
I believe so, yes.
I'm not aware of any _really bad_ issues with LED subsystem in
4.9. Take a look at changelog of
2b83ff96f51d0b039c4561b9f95c824d7bddb85c -- it fixes rather
theoretical issue; user can reproduce it by hand in shell, but,
well... don't do it then.
The rest of fixes ... fix some more theoretical races. I don't think
it is -stable material, as I pointed out before.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-03-13 13:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180203180015.29073-1-alexander.levin@microsoft.com>
2018-02-03 18:00 ` [PATCH AUTOSEL for 4.14 065/110] led: core: Fix brightness setting when setting delay_off=0 Sasha Levin
2018-02-03 20:35 ` Pavel Machek
2018-02-04 0:30 ` Sasha Levin
2018-02-04 9:05 ` Pavel Machek
2018-02-04 11:15 ` Greg KH
2018-02-04 17:17 ` Pavel Machek
2018-02-06 2:02 ` Sasha Levin
2018-02-06 20:44 ` Jacek Anaszewski
2018-03-12 15:00 ` Matthias Schiffer
2018-03-12 15:28 ` Greg KH
2018-03-12 15:45 ` Matthias Schiffer
2018-03-12 20:20 ` Jacek Anaszewski
2018-03-13 7:50 ` Pavel Machek
2018-03-13 9:37 ` Greg KH
2018-03-13 13:27 ` Pavel Machek [this message]
2018-03-13 19:44 ` Jacek Anaszewski
2018-03-16 12:46 ` Greg KH
2018-02-06 21:51 ` Pavel Machek
2018-02-04 15:49 ` Sasha Levin
2018-02-04 17:31 ` Pavel Machek
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=20180313132748.GA20246@amd \
--to=pavel@ucw.cz \
--cc=Alexander.Levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=matthieu.castet@parrot.com \
--cc=mschiffer@universe-factory.net \
--cc=stable@vger.kernel.org \
/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).