From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Sasha Levin <Alexander.Levin@microsoft.com>, Pavel Machek <pavel@ucw.cz>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"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, 6 Feb 2018 21:44:58 +0100 [thread overview]
Message-ID: <713113d8-7662-d80c-c62f-af020469d0bf@gmail.com> (raw)
In-Reply-To: <20180206020210.m6gl7vai4p6azb6s@sasha-lappy>
On 02/06/2018 03:02 AM, Sasha Levin wrote:
> On Sun, Feb 04, 2018 at 06:17:36PM +0100, Pavel Machek wrote:
>>
>>>>>>> *** if brightness=0, led off
>>>>>>> *** else apply brightness if next timer <--- timer is stop, and will never apply new setting
>>>>>>> ** otherwise set led_set_brightness_nosleep
>>>>>>>
>>>>>>> To fix that, when we delete the timer, we should clear LED_BLINK_SW.
>>>>>>
>>>>>> Can you run the tests on the affected stable kernels? I have feeling
>>>>>> that the problem described might not be present there.
>>>>>
>>>>> Hm, I don't seem to have HW to test that out. Maybe someone else does?
>>>>
>>>> Why are you submitting patches you have no way to test?
>>>
>>> What? This is stable tree backporting, why are you trying to make a
>>> requirement for something that we have never had before?
>>
>> I don't think random patches should be sent to stable just because
>> they appeared in mainline. Plus, I don't think I'm making new rules:
>>
>> submit-checklist.rst:
>>
>> 13) Has been build- and runtime tested with and without ``CONFIG_SMP``
>> and
>> ``CONFIG_PREEMPT.``
>>
>> stable-kernel-rules.rst:
>>
>> Rules on what kind of patches are accepted, and which ones are not,
>> into the "-stable" tree:
>>
>> - It must be obviously correct and tested.
>> - It must fix a real bug that bothers people (not a, "This could be a
>> problem..." type thing).
>
> So you're saying that this doesn't qualify as a bug?
>
>>> This is a backport of a patch that is already upstream. If it doesn't
>>> belong in a stable tree, great, let us know that, saying why it is so.
>>
>> See jacek.anaszewski@gmail.com 's explanation.
>
> I might be missing something, but Jacek suggested I pull another patch
> before this one?
Just to clarify:
For 4.14 below patches are chosen correctly:
[PATCH AUTOSEL for 4.14 065/110] led: core: Fix brightness setting when
setting delay_off=0
[PATCH AUTOSEL for 4.14 094/110] leds: core: Fix regression caused by
commit 2b83ff96f51d
For 4.9 both above patches are needed preceded by:
eb1610b4c273 ("led: core: Fix blink_brightness setting race")
The issue the patch [PATCH AUTOSEL for 4.14 065/110] fixes was
introduced in 4.7, and thus it should be removed from the series
for 3.18 and 4.4.
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2018-02-06 20:44 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 [this message]
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
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=713113d8-7662-d80c-c62f-af020469d0bf@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=Alexander.Levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=matthieu.castet@parrot.com \
--cc=pavel@ucw.cz \
--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).