linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	kernel list <linux-kernel@vger.kernel.org>,
	jacek.anaszewski@gmail.com, linux-leds@vger.kernel.org
Subject: [GIT PULL] LEDs changes for v5.14-rc1
Date: Sat, 3 Jul 2021 15:34:32 +0200	[thread overview]
Message-ID: <20210703133432.GA30301@amd> (raw)

[-- Attachment #1: Type: text/plain, Size: 4488 bytes --]

The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:

  Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git/ tags/leds-5.14-rc1

for you to fetch changes up to 7b97174cc93fadb055258f4f8f3b964e9968e59f:

  leds: lgm: Fix up includes (2021-06-24 00:55:41 +0200)

----------------------------------------------------------------
This contains quite a lot of fixes, with more fixes in my inbox that
did not make it (sorry).

----------------------------------------------------------------
Andy Shevchenko (16):
      leds: class: The -ENOTSUPP should never be seen by user space
      leds: el15203000: Introduce to_el15203000_led() helper
      leds: lgm-sso: Fix clock handling
      leds: lgm-sso: Remove unneeded of_match_ptr()
      leds: lgm-sso: Drop duplicate NULL check for GPIO operations
      leds: lm3532: select regmap I2C API
      leds: lm3532: Make error handling more robust
      leds: lm36274: Put fwnode in error case during ->probe()
      leds: lm36274: Correct headers (of*.h -> mod_devicetable.h)
      leds: lm3692x: Put fwnode in any case during ->probe()
      leds: lm3697: Don't spam logs when probe is deferred
      leds: lp50xx: Put fwnode in error case during ->probe()
      leds: lt3593: Make use of device properties
      leds: pwm: Make error handling more robust
      leds: el15203000: Make error handling more robust
      leds: lm36274: Add missed property.h

Christophe JAILLET (1):
      leds: ktd2692: Fix an error handling path

Doug Zobel (1):
      leds: lp55xx: Initialize enable GPIO direction to output

Lee Jones (14):
      leds: trigger: ledtrig-cpu: Fix incorrectly documented param 'ledevt'
      leds: leds-gpio-register: Supply description for param 'id'
      leds: led-class: Fix incorrectly documented param 'dev'
      leds: leds-bcm6328: Demote kernel-doc abuse
      leds: leds-as3645a: Fix function name 'as3645a_set_current()'
      leds: leds-blinkm: Remove unused variable 'ret'
      leds: leds-is31fl32xx: Provide missing description for member 'sw_shutdown_func'
      leds: leds-lp3944: Provide missing function names in documentation headers
      leds: leds-lm3530: Fix incorrect spelling of 'brightness'
      leds: leds-lm3692x: Fix some kernel-doc formatting issues
      leds: leds-lm3697: Provide some missing descriptions for struct members
      leds: leds-mlxreg: Fix incorrect documentation of struct member 'led_cdev' and 'led_cdev_name'
      leds: leds-lp8860: Fix kernel-doc related formatting issues
      leds: leds-mlxcpld: Fix a bunch of kernel-doc formatting issues

Linus Walleij (1):
      leds: lgm: Fix up includes

Yang Yingliang (1):
      leds: tlc591xx: fix return value check in tlc591xx_probe()

Zhen Lei (1):
      leds: as3645a: Fix error return code in as3645a_parse_node()

Zou Wei (1):
      leds: turris-omnia: add missing MODULE_DEVICE_TABLE

 drivers/leds/Kconfig               |  2 +-
 drivers/leds/blink/leds-lgm-sso.c  | 53 ++++++++++++++++----------------------
 drivers/leds/led-class.c           |  6 +----
 drivers/leds/leds-as3645a.c        |  3 ++-
 drivers/leds/leds-bcm6328.c        |  2 +-
 drivers/leds/leds-blinkm.c         |  5 ++--
 drivers/leds/leds-el15203000.c     | 37 +++++++++++---------------
 drivers/leds/leds-gpio-register.c  |  1 +
 drivers/leds/leds-is31fl32xx.c     |  3 ++-
 drivers/leds/leds-ktd2692.c        | 27 ++++++++++++-------
 drivers/leds/leds-lm3530.c         |  2 +-
 drivers/leds/leds-lm3532.c         |  7 ++---
 drivers/leds/leds-lm36274.c        |  4 ++-
 drivers/leds/leds-lm3692x.c        | 26 +++++++++----------
 drivers/leds/leds-lm3697.c         | 12 +++++----
 drivers/leds/leds-lp3944.c         |  6 ++---
 drivers/leds/leds-lp50xx.c         |  2 +-
 drivers/leds/leds-lp55xx-common.c  |  2 +-
 drivers/leds/leds-lp8860.c         | 16 ++++++------
 drivers/leds/leds-lt3593.c         |  8 +++---
 drivers/leds/leds-mlxcpld.c        | 38 +++++++++++++--------------
 drivers/leds/leds-mlxreg.c         |  3 ++-
 drivers/leds/leds-pwm.c            | 16 +++++++-----
 drivers/leds/leds-tlc591xx.c       |  8 ++++--
 drivers/leds/leds-turris-omnia.c   |  1 +
 drivers/leds/trigger/ledtrig-cpu.c |  2 +-
 26 files changed, 145 insertions(+), 147 deletions(-)


-- 
http://www.livejournal.com/~pavelmachek

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

             reply	other threads:[~2021-07-03 13:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03 13:34 Pavel Machek [this message]
2021-07-03 19:40 ` [GIT PULL] LEDs changes for v5.14-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=20210703133432.GA30301@amd \
    --to=pavel@ucw.cz \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --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).