linux-kernel - Re: [PATCH] HID: hid-input: only ignore 0 battery events for digitizers

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: <nsz6llo4nsg4zuiogmewuccl76nzjjijgkjzqeazzs33lj4phc@k5rskuabbsz2>
Date: Tue, 14 Oct 2025 21:31:10 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Jiri Kosina <jikos@...nel.org>
Cc: Benjamin Tissoires <bentiss@...nel.org>, 
	卢国宏 <luguohong@...omi.com>, kenalba@...gle.com, linux-input@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] HID: hid-input: only ignore 0 battery events for
 digitizers

Hi Jiri,

On Tue, Oct 14, 2025 at 12:25:25PM +0200, Jiri Kosina wrote:
> 
> Hi Dmitry,
> 
> thanks for the fix. It doesn't apply cleanly on a reasonably recent tree 
> though, as since e94536e1d1818b09 we're already propagating usage to 
> hidinput_update_battery(), and we're issuing explicit call to 
> power_supply_changed() as well.
> 
> Could you please refresh on a more recent codebase and resubmit? I could 
> do that myself, but I guess you also have a way to test the patch with 
> your use-case ... ?

Sorry about that, I made the patch on top of my tree which lags behind.
I just sent a v2 rebased on top of linux-next.

I actually do not have the hardware to test, we have to rely on 卢国宏
to do it for us.

Thanks.

-- 
Dmitry