linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Waqar Hameed <waqar.hameed@axis.com>
To: Sebastian Reichel <sre@kernel.org>,
	Tobias Schrammm <t.schramm@manjaro.org>,
	Matti Vaittinen <mazziesaccount@gmail.com>
Cc: <kernel@axis.com>, <linux-pm@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: [PATCH 0/5] power: supply: Remove unused gpio include header
Date: Sat, 20 Dec 2025 22:39:55 +0100	[thread overview]
Message-ID: <pndh5tkzvbo.a.out@axis.com> (raw)

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...

[1] https://www.ti.com/product/BQ25630

Waqar Hameed (5):
  power: supply: bd99954: Remove unused gpio include header
  power: supply: bq256xx: Remove unused gpio include header
  power: supply: bq25980: Remove unused gpio include header
  power: supply: cw2015: Remove unused gpio include header
  power: supply: ucs1002: Remove unused gpio include header

 drivers/power/supply/bd99954-charger.c | 1 -
 drivers/power/supply/bq256xx_charger.c | 1 -
 drivers/power/supply/bq25980_charger.c | 1 -
 drivers/power/supply/cw2015_battery.c  | 1 -
 drivers/power/supply/ucs1002_power.c   | 1 -
 5 files changed, 5 deletions(-)


base-commit: fa084c35afa13ab07a860ef0936cd987f9aa0460
-- 
2.39.5


             reply	other threads:[~2025-12-20 21:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-20 21:39 Waqar Hameed [this message]
2025-12-20 21:56 ` [PATCH 0/5] power: supply: Remove unused gpio include header Waqar Hameed
  -- strict thread matches above, loose matches on Subject: below --
2025-12-20 21:54 Waqar Hameed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pndh5tkzvbo.a.out@axis.com \
    --to=waqar.hameed@axis.com \
    --cc=kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mazziesaccount@gmail.com \
    --cc=sre@kernel.org \
    --cc=t.schramm@manjaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).