linux-kernel - Re: "Say Y" on CONFIG_LEDS_TRIGGER

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <e621b590-422d-bab5-72da-da21da8f9fd6@gmail.com>
Date:   Tue, 19 Sep 2017 22:05:11 +0200
From:   Jacek Anaszewski <jacek.anaszewski@...il.com>
To:     Pavel Machek <pavel@....cz>, linux-leds@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: "Say Y" on CONFIG_LEDS_TRIGGER_ACTIVITY

Hi Pavel,

On 09/19/2017 09:50 PM, Pavel Machek wrote:
> Hi!
> 
> Help text says:
> 
> CONFIG_LEDS_TRIGGER_ACTIVITY:
> 
> This allows LEDs to be controlled by a immediate CPU usage.
> The flash frequency and duty cycle varies from faint flashes to
> intense brightness depending on the instant CPU load.
> If unsure, say Y.
> 
> I don't believe this is important enough trigger that we should
> suggest it by default. So I believe this should be changed to "say N".

Thanks for the heads-up.
Fixed the related commit on the for-next branch of linux-leds.git.

-- 
Best regards,
Jacek Anaszewski