From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Fainelli Subject: Re: [PATCH 2/2] ARM: dts: BCM5301X: Don't use nonexistent "default-off" LED trigger Date: Thu, 9 Mar 2017 12:33:46 -0800 Message-ID: References: <20170308064105.26619-1-zajec5@gmail.com> <20170308064105.26619-2-zajec5@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <20170308064105.26619-2-zajec5@gmail.com> Sender: linux-leds-owner@vger.kernel.org To: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= , Florian Fainelli Cc: Rob Herring , Mark Rutland , Russell King , Hauke Mehrtens , bcm-kernel-feedback-list@broadcom.com, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-leds@vger.kernel.org, =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= List-Id: devicetree@vger.kernel.org On 03/07/2017 10:41 PM, Rafał Miłecki wrote: > From: Rafał Miłecki > > 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 Applied, thanks! -- Florian