linux-kernel - Re: [PATCH v3] HID: corsair-void: Update power supply values with a unified work handler

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: <CALTg27kDRv+_y9qS3eCZUaQ6f5A-P8Y2GFyL-EMHZxixW=jYaw@mail.gmail.com>
Date: Fri, 14 Feb 2025 13:32:19 +0000
From: Stuart <stuart.a.hayhurst@...il.com>
To: Jiri Slaby <jirislaby@...nel.org>
Cc: linux-input@...r.kernel.org, Jiri Kosina <jikos@...nel.org>, 
	Benjamin Tissoires <bentiss@...nel.org>, linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH v3] HID: corsair-void: Update power supply values with a
 unified work handler

> Now I think, what is actually expected to happen if both add_battery and
> remove_battery is set? Do nothing as the code does?

It means that either the headset connected and then disconnected again, or
it disconnected and reconnected again. Either way, the battery should be left
in its current state.

Of course it could connect, disconnect and connect again to end up in
that state,
but if the driver is 3 events (a physical action) behind, we're already done for

Stuart