From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: bin.lan.cn@eng.windriver.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1] leds: an30259a: Use devm_mutex_init() for mutex initialization
Date: Fri, 13 Dec 2024 10:13:21 -0500 [thread overview]
Message-ID: <20241213092600-73e71f5a8637be06@stable.kernel.org> (raw)
In-Reply-To: <20241213035206.3518851-1-bin.lan.cn@eng.windriver.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: c382e2e3eccb6b7ca8c7aff5092c1668428e7de6
WARNING: Author mismatch between patch and upstream commit:
Backport author: bin.lan.cn@eng.windriver.com
Commit author: George Stark <gnstark@salutedevices.com>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 3ead19aa341d)
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
1: c382e2e3eccb6 ! 1: c7a5b2d87541f leds: an30259a: Use devm_mutex_init() for mutex initialization
@@ Metadata
## Commit message ##
leds: an30259a: Use devm_mutex_init() for mutex initialization
+ [ Upstream commit c382e2e3eccb6b7ca8c7aff5092c1668428e7de6 ]
+
In this driver LEDs are registered using devm_led_classdev_register()
so they are automatically unregistered after module's remove() is done.
led_classdev_unregister() calls module's led_set_brightness() to turn off
@@ Commit message
Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Link: https://lore.kernel.org/r/20240411161032.609544-9-gnstark@salutedevices.com
Signed-off-by: Lee Jones <lee@kernel.org>
+ [ Resolve merge conflict in drivers/leds/leds-an30259a.c ]
+ Signed-off-by: Bin Lan <bin.lan.cn@windriver.com>
## drivers/leds/leds-an30259a.c ##
@@ drivers/leds/leds-an30259a.c: static int an30259a_probe(struct i2c_client *client)
@@ drivers/leds/leds-an30259a.c: static int an30259a_probe(struct i2c_client *clien
{ .compatible = "panasonic,an30259a", },
{ /* sentinel */ },
@@ drivers/leds/leds-an30259a.c: static struct i2c_driver an30259a_driver = {
- .of_match_table = an30259a_match_table,
+ .of_match_table = of_match_ptr(an30259a_match_table),
},
- .probe = an30259a_probe,
+ .probe_new = an30259a_probe,
- .remove = an30259a_remove,
.id_table = an30259a_id,
};
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
prev parent reply other threads:[~2024-12-13 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 3:52 [PATCH 6.1] leds: an30259a: Use devm_mutex_init() for mutex initialization bin.lan.cn
2024-12-13 11:15 ` Greg KH
2024-12-13 15:13 ` Sasha Levin [this message]
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=20241213092600-73e71f5a8637be06@stable.kernel.org \
--to=sashal@kernel.org \
--cc=bin.lan.cn@eng.windriver.com \
--cc=stable@vger.kernel.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