linux-kernel - Re: [PATCH 0/5] power: supply: Remove unused gpio include header

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] [day] [month] [year] [list]

Message-Id: <176818296396.643060.5342827931953504236.b4-ty@collabora.com>
Date: Mon, 12 Jan 2026 02:56:03 +0100
From: Sebastian Reichel <sebastian.reichel@...labora.com>
To: Sebastian Reichel <sre@...nel.org>, 
 Tobias Schrammm <t.schramm@...jaro.org>, 
 Matti Vaittinen <mazziesaccount@...il.com>, 
 Waqar Hameed <waqar.hameed@...s.com>
Cc: kernel@...s.com, linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] power: supply: Remove unused gpio include header


On Sat, 20 Dec 2025 22:54:07 +0100, Waqar Hameed wrote:
> These drivers include the gpio header but never use it. This patch
> series just removes this unnecessary header.
> 
> This issue was found when writing a new driver for the upcoming TI
> BQ25630 [1]. Patch adding support for that one will be sent as soon as
> TI releases the datasheet publicly, which should be anytime soon...
> 
> [...]

Applied, thanks!

[1/5] power: supply: bd99954: Remove unused gpio include header
      commit: e312b7e3183d2d806609ee0e905da807ff5d891f
[2/5] power: supply: bq256xx: Remove unused gpio include header
      commit: 38673fd9d622318eed1e35cfad5998b4056edc1e
[3/5] power: supply: bq25980: Remove unused gpio include header
      commit: 3d74b6dfd703ba812c624c689451b0ae573b4f0b
[4/5] power: supply: cw2015: Remove unused gpio include header
      commit: 91a4f92de8454621e9d4e77a58c19c9d60a69581
[5/5] power: supply: ucs1002: Remove unused gpio include header
      commit: ce3bc8469e4c387fd937e2ef96a6d45b7e22afc7

Best regards,
-- 
Sebastian Reichel <sebastian.reichel@...labora.com>