On 8 March 2017 at 18:31, Florian Fainelli <f.fainelli@xxxxxxxxx> wrote:
> On 03/07/2017 10:41 PM, Rafał Miłecki wrote:
>> From: Rafał Miłecki <rafal@xxxxxxxxxx>
>>
>> Such a trigger doesn't exist in Linux and is not needed as LED is being
>> turned off by default. This could cause errors in LEDs core code when
>> trying to set default trigger.
>>
>> Signed-off-by: Rafał Miłecki <rafal@xxxxxxxxxx>
>
> Since you are fixing something, what's the proper Fixes: tag for this
> commit? Likewise for the second patch.
This problem was exposed by the commit f363a870eaef ("leds: core: use
deferred probing if default trigger isn't available yet") pushed to
the:
https://git.kernel.org/cgit/linux/kernel/git/j.anaszewski/linux-leds.git/log/?h=for-next
I reported problems caused by this commit in e-mail thread
New problems after f363a870eaef ("leds: core: use deferred probing if
default trigger isn't available yet")
(I can't access linux-leds archive) and it was dropped after my report.
So there is nothing to point in the "Fixes:".
--
Rafał
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
