From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
jacek.anaszewski@gmail.com, krzk@kernel.org, robh@kernel.org,
tiny.windzz@gmail.com
Subject: [GIT PULL] LED updates for 4.21-rc1
Date: Fri, 21 Dec 2018 16:54:51 +0100 [thread overview]
Message-ID: <20181221155451.7024-1-jacek.anaszewski@gmail.com> (raw)
Hi Linus,
Please pull LED updates for 4.21-rc1.
There are several few-liners, where most of them are fixes
and improvments. One thing standing out is ground preparation
for inititializing trigger parameters via Device Tree.
We introduce LED_INIT_DEFAULT_TRIGGER flag for that purpose
and set it when default trigger is matched. It indicates
that trigger should parse DT properties to retrieve
the initialization data when set as default one.
The following changes since commit 9ff01193a20d391e8dbce4403dd5ef87c7eaaca6:
Linux 4.20-rc3 (2018-11-18 13:33:44 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git tags/leds-for-4.21-rc1
for you to fetch changes up to 8146aace60c7409cc60a1598bc9647a5bbb12eb4:
led: triggers: Initialize LED_INIT_DEFAULT_TRIGGER if trigger is brought after class (2018-12-10 21:31:55 +0100)
Thanks,
Jacek Anaszewski
----------------------------------------------------------------
LEDs for 4.21-rc1
----------------------------------------------------------------
Jacek Anaszewski (2):
led: triggers: Break the for loop after default trigger is found
led: triggers: Add LED_INIT_DEFAULT_TRIGGER flag
Krzysztof Kozlowski (4):
leds: gpio: Drop unneeded manual of_node assignment
leds: pwm: Simplify with resource-managed devm_led_classdev_register()
leds: pwm: Use OF variant of LED registering function
led: triggers: Initialize LED_INIT_DEFAULT_TRIGGER if trigger is brought after class
Rob Herring (1):
leds: 88pm860x: Use of_node_name_eq for node name comparisons
Yangtao Li (1):
leds: powernv: add of_node_put()
drivers/leds/led-triggers.c | 9 +++++++--
drivers/leds/leds-88pm860x.c | 2 +-
drivers/leds/leds-gpio.c | 1 -
drivers/leds/leds-powernv.c | 12 +++++++++---
drivers/leds/leds-pwm.c | 22 ++--------------------
include/linux/leds.h | 1 +
6 files changed, 20 insertions(+), 27 deletions(-)
next reply other threads:[~2018-12-21 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 15:54 Jacek Anaszewski [this message]
2018-12-25 23:20 ` [GIT PULL] LED updates for 4.21-rc1 pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181221155451.7024-1-jacek.anaszewski@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tiny.windzz@gmail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).