Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Rasmus Villemoes <linux@rasmusvillemoes.dk>
To:     Pavel Machek <pavel@ucw.cz>,
        =?UTF-8?q?Uwe=20Kleine-K=C3=B6nig?= 
        <u.kleine-koenig@pengutronix.de>,
        Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc:     LKML <linux-kernel@vger.kernel.org>,
        Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: [PATCH 0/4] leds: netdev trigger: allow setting initial values in device tree
Date:   Wed, 13 Mar 2019 21:26:11 +0100
Message-Id: <20190313202615.22883-1-linux@rasmusvillemoes.dk>
In-Reply-To: <20190311144227.GA4404@amd>
References: <20190311144227.GA4404@amd>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

I asked whether it would be reasonable to be able to initialize a
netdev trigger from DT data and was told "patch welcome", so here's an
attempt at implementing that, adding some pieces of documentation
along the way that would have saved me some time figuring out how to
transition away from the deprecated CONFIG_CAN_LEDS.

Rasmus Villemoes (4):
  leds: netdev trigger: use memcpy in device_name_store
  leds: netdev trigger: factor out middle part of device_name_store
  leds: netdev trigger: add documentation to leds/common.txt
  leds: netdev trigger: allow setting initial values in device tree

 .../devicetree/bindings/leds/common.txt       | 20 ++++++
 drivers/leds/trigger/ledtrig-netdev.c         | 64 +++++++++++++++----
 drivers/net/can/Kconfig                       |  3 +-
 3 files changed, 73 insertions(+), 14 deletions(-)

-- 
2.20.1