On 10. 02. 25, 21:32, Stuart wrote:
Anyway, maybe I misunderstand, please send a patch and we will see ;)
Nope, you're right, I gave the spinlocks a test and it did not like that at all
In that case, I can just move the power_supply_changed call into its own
work and then schedule that from corsair_void_process_receiver()?
And what about having one work for all three (reg, up, unreg) as I
suggested. As I wrote, IMO, you would need no lock then. Only flags to
see what to do there.
thanks,
--
js
suse labs
