Jacek
On 7/30/19 4:11 PM, Dan Murphy wrote:
Jacek
On 7/30/19 3:47 PM, Dan Murphy wrote:
Jacek
On 7/30/19 3:30 PM, Jacek Anaszewski wrote:
Hi Dan,
On 7/30/19 8:40 PM, Dan Murphy wrote:
Jacek
Did you see/fix this on the led-next branch?
I saw this when booting trying to fix the lm3532
[ 8.651461] led_class: exports duplicate symbol
devm_led_classdev_register_ext (owned by kernel)
[ 8.730063] led_class: exports duplicate symbol
devm_led_classdev_register_ext (owned by kernel)
I've just tried next-20190730 and haven't noticed anything like that.
I've checked both with driver compiled-in and loaded as a module.
[...]
Try configuring the LEDS_CLASS as a built-in module.
-CONFIG_LEDS_CLASS=m
+CONFIG_LEDS_CLASS=y
I am also on for-next
I figured it out. I had old modules which had the led_class as a module
as opposed to a
built in.
Sorry for the noise
Dan
Dan
