linux-kernel - Re: [PATCH] leds: use default-on trigger for Cobalt Qube

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: <200912041501.37415.florian@openwrt.org>
Date:	Fri, 4 Dec 2009 15:01:37 +0100
From:	Florian Fainelli <florian@...nwrt.org>
To:	Richard Purdie <rpurdie@...ys.net>
Cc:	linux-kernel@...r.kernel.org, linux-mips@...ux-mips.org,
	Martin Michlmayr <tbm@...ius.com>,
	Sameer Verma <sverma@...u.edu>
Subject: Re: [PATCH] leds: use default-on trigger for Cobalt Qube

Richard,

Did you get this patch? Thanks.

On Thursday 26 November 2009 19:41:02 Regards, Florian Fainelli wrote:
> This patch changes the default trigger from "ide-disk"
> to "default-on". Users updating from kernels not having this
> LED driver will prefer having the same LED behavior as they
> used to.
> 
> Signed-off-by: Florian Fainelli <florian@...nwrt.org>
> ---
> diff --git a/drivers/leds/leds-cobalt-qube.c
>  b/drivers/leds/leds-cobalt-qube.c index 8816806..81b2014 100644
> --- a/drivers/leds/leds-cobalt-qube.c
> +++ b/drivers/leds/leds-cobalt-qube.c
> @@ -31,7 +31,7 @@ static struct led_classdev qube_front_led = {
>  	.name			= "qube::front",
>  	.brightness		= LED_FULL,
>  	.brightness_set		= qube_front_led_set,
> -	.default_trigger	= "ide-disk",
> +	.default_trigger	= "default-on",
>  };
> 
>  static int __devinit cobalt_qube_led_probe(struct platform_device *pdev)
> 

-- 
Regards, Florian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/