On 04/06/2016 06:38 AM, Ezequiel Garcia wrote:
On 5 April 2016 at 18:36, Jacek Anaszewski wrote:
Hi Ezequiel,
On 04/04/2016 10:22 PM, Ezequiel Garcia wrote:
Now that we can mark any LED (even those in use by delayed blink
triggers) to trigger on a kernel panic, let's introduce a nosleep
led
On 5 April 2016 at 18:36, Jacek Anaszewski wrote:
> Hi Ezequiel,
>
>
> On 04/04/2016 10:22 PM, Ezequiel Garcia wrote:
>>
>> Now that we can mark any LED (even those in use by delayed blink
>> triggers) to trigger on a kernel panic, let's introduce a nosleep
>> led_trigger_event API.
>>
>> This API
Hi Ezequiel,
On 04/04/2016 10:22 PM, Ezequiel Garcia wrote:
Now that we can mark any LED (even those in use by delayed blink
triggers) to trigger on a kernel panic, let's introduce a nosleep
led_trigger_event API.
This API is needed to skip the delayed blink path on
led_trigger_event. LEDs that
Now that we can mark any LED (even those in use by delayed blink
triggers) to trigger on a kernel panic, let's introduce a nosleep
led_trigger_event API.
This API is needed to skip the delayed blink path on
led_trigger_event. LEDs that are switched on a kernel panic,
might be in use by a delayed b
4 matches
Mail list logo