linux-kernel - Re: [PATCH v5] HID: corsair-void: Add Corsair Void headset family driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8b27c399-098c-48b7-b71d-a833594571af@kernel.org>
Date: Tue, 11 Feb 2025 06:36:57 +0100
From: Jiri Slaby <jirislaby@...nel.org>
To: Stuart <stuart.a.hayhurst@...il.com>
Cc: linux-input@...r.kernel.org, Jiri Kosina <jikos@...nel.org>,
 Benjamin Tissoires <bentiss@...nel.org>,
 Christophe JAILLET <christophe.jaillet@...adoo.fr>,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5] HID: corsair-void: Add Corsair Void headset family
 driver

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