linux-kernel - [PATCH 0/4] leds: netdev trigger: allow setting initial values in device tree

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20190313202615.22883-1-linux@rasmusvillemoes.dk>
Date:   Wed, 13 Mar 2019 21:26:11 +0100
From:   Rasmus Villemoes <linux@...musvillemoes.dk>
To:     Pavel Machek <pavel@....cz>,
        Uwe Kleine-König 
        <u.kleine-koenig@...gutronix.de>,
        Jacek Anaszewski <jacek.anaszewski@...il.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Rasmus Villemoes <linux@...musvillemoes.dk>
Subject: [PATCH 0/4] leds: netdev trigger: allow setting initial values in device tree

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