summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndy Shevchenko <andriy.shevchenko@linux.intel.com>2026-03-27 11:27:29 +0100
committerLee Jones <lee@kernel.org>2026-04-09 13:49:19 +0100
commit7a43ccf85dfe06eef483c034e68b81ff326741aa (patch)
tree335b7363d0e91d50b83d5f15675d28409ca4f2ed
parentb6de441f8ce22e3ead3b858342fe5652598a3572 (diff)
leds: class: Make led_remove_lookup() NULL-aware
It is a usual pattern in the kernel to make releasing functions be NULL-aware so they become a no-op. This helps reducing unneeded checks in the code where the given resource is optional. Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Link: https://patch.msgid.link/20260327102729.797254-1-andriy.shevchenko@linux.intel.com Signed-off-by: Lee Jones <lee@kernel.org>
-rw-r--r--drivers/leds/led-class.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/drivers/leds/led-class.c b/drivers/leds/led-class.c
index 8d7ec9ccb173..9e14ae588f78 100644
--- a/drivers/leds/led-class.c
+++ b/drivers/leds/led-class.c
@@ -421,6 +421,9 @@ EXPORT_SYMBOL_GPL(led_add_lookup);
*/
void led_remove_lookup(struct led_lookup_data *led_lookup)
{
+ if (!led_lookup)
+ return;
+
mutex_lock(&leds_lookup_lock);
list_del(&led_lookup->list);
mutex_unlock(&leds_lookup_lock);