public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Pavel Machek <pavel@ucw.cz>
Subject: [GIT PULL] LEDs for v7.1
Date: Mon, 20 Apr 2026 09:20:24 +0100	[thread overview]
Message-ID: <20260420082024.GB3202366@google.com> (raw)

Good morning Linus,

The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:

  Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git tags/leds-next-7.1

for you to fetch changes up to 7a43ccf85dfe06eef483c034e68b81ff326741aa:

  leds: class: Make led_remove_lookup() NULL-aware (2026-04-09 13:49:19 +0100)

----------------------------------------------------------------
LEDs for v7.1

  * Core:
    * Implement fallback to software node name for LED names
    * Fix formatting issues in `led-core.c` reported by checkpatch.pl
    * Make `led_remove_lookup()` NULL-aware
    * Switch from `class_find_device_by_of_node()` to `class_find_device_by_fwnode()`
  * LGM SSO:
    * Fix a typo in the `GET_SRC_OFFSET` macro
  * Multicolor:
    * Fix a signedness error by changing the `intensity_value` type to `unsigned int`
  * Qualcomm LPG:
    * Prevent array overflow when selecting high-resolution values
  * TI LP8860:
    * Do not unconditionally program the EEPROM on probe
    * Hold the mutex lock for the entirety of the EEPROM programming process

  * Kinetic KTD2692:
    * Make the `ktd2692_timing` variable static to resolve a sparse warning
  * LGM SSO:
    * Remove a duplicate assignment of `priv->mmap` in `intel_sso_led_probe()`
  * TTY Trigger:
    * Prefer `IS_ERR_OR_NULL()` over manual NULL checks
  * TI LM3642:
    * Use `guard(mutex)` to simplify locking and avoid manual `mutex_unlock()` calls
  * TI LP5569:
    * Use `sysfs_emit()` instead of `sprintf()` for sysfs outputs
  * TI LP8860:
    * Return directly from `lp8860_init()` instead of using empty `goto` statements
    * Use a single regmap table and an access table instead of separate maps for normal and EEPROM registers
    * Remove an unused read of the `STATUS` register during EEPROM programming

  * Core:
    * Drop the unneeded dependency on `OF_GPIO` from `LEDS_NETXBIG` in Kconfig

  * Spreadtrum SC2731:
    * Add a compatible string for the SC2730 PMIC LED controller
  * TI LP5860:
    * Add the `enable-gpios` property for the `VIO_EN` pin

----------------------------------------------------------------
Andrew Davis (5):
      leds: lp8860: Use a single regmap table
      leds: lp8860: Return directly from lp8860_init
      leds: lp8860: Hold lock for all of EEPROM programming
      leds: lp8860: Remove unused read of STATUS register
      leds: lp8860: Do not always program EEPROM on probe

Andy Shevchenko (1):
      leds: class: Make led_remove_lookup() NULL-aware

Bartosz Golaszewski (1):
      leds: Kconfig: Drop unneeded dependency on OF_GPIO

Chen Ni (1):
      leds: lgm-sso: Remove duplicate assignments for priv->mmap

Dmitry Torokhov (3):
      leds: core: Implement fallback to software node name for LED names
      leds: core: Fix formatting issues
      leds: led-class: Switch to using class_find_device_by_fwnode()

Greg Kroah-Hartman (1):
      leds: qcom-lpg: Check for array overflow when selecting the high resolution

Krzysztof Kozlowski (1):
      leds: ktd2692: Make ktd2692_timing variable static

Lukas Kraft (1):
      leds: lgm-sso: Fix typo in macro for src offset

Michael Tretter (1):
      leds: multicolor: Change intensity_value to unsigned int

Neel Bullywon (1):
      leds: lp5569: Use sysfs_emit instead of sprintf()

Otto Pflüger (1):
      dt-bindings: leds: sc2731: Add compatible for SC2730

Philipp Hahn (1):
      leds: Prefer IS_ERR_OR_NULL over manual NULL check

Richard Lyu (1):
      leds: lm3642: Use guard to simplify locking

Steffen Trumtrar (1):
      dt-bindings: leds: lp5860: add enable-gpio

 .../devicetree/bindings/leds/leds-lp5860.yaml      |   7 ++
 .../devicetree/bindings/leds/sprd,sc2731-bltc.yaml |   7 +-
 drivers/leds/Kconfig                               |   1 -
 drivers/leds/blink/leds-lgm-sso.c                  |   4 +-
 drivers/leds/flash/leds-ktd2692.c                  |   2 +-
 drivers/leds/led-class-multicolor.c                |   4 +-
 drivers/leds/led-class.c                           |   5 +-
 drivers/leds/led-core.c                            |  20 ++--
 drivers/leds/leds-lm3642.c                         |  18 ++--
 drivers/leds/leds-lp5569.c                         |   4 +-
 drivers/leds/leds-lp8860.c                         | 111 +++++++++------------
 drivers/leds/rgb/leds-qcom-lpg.c                   |   7 +-
 drivers/leds/trigger/ledtrig-tty.c                 |   2 +-
 13 files changed, 98 insertions(+), 94 deletions(-)

-- 
Lee Jones [李琼斯]


             reply	other threads:[~2026-04-20  8:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20  8:20 Lee Jones [this message]
2026-04-20 19:13 ` [GIT PULL] LEDs for v7.1 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=20260420082024.GB3202366@google.com \
    --to=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --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