From: linux@treblig.org
To: linus.walleij@linaro.org, mazziesaccount@gmail.com, sre@kernel.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
"Dr. David Alan Gilbert" <linux@treblig.org>
Subject: [PATCH 1/2] power: supply: bd99954: remove unused struct 'battery_data'
Date: Tue, 28 May 2024 01:06:33 +0100 [thread overview]
Message-ID: <20240528000634.196707-2-linux@treblig.org> (raw)
In-Reply-To: <20240528000634.196707-1-linux@treblig.org>
From: "Dr. David Alan Gilbert" <linux@treblig.org>
'battery_data' is unused since the original
commit 0902f8366491 ("power: supply: Support ROHM bd99954 charger").
Remove it.
Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
---
drivers/power/supply/bd99954-charger.c | 7 -------
1 file changed, 7 deletions(-)
diff --git a/drivers/power/supply/bd99954-charger.c b/drivers/power/supply/bd99954-charger.c
index 1ed1d9f99fb3..54bf88262510 100644
--- a/drivers/power/supply/bd99954-charger.c
+++ b/drivers/power/supply/bd99954-charger.c
@@ -70,13 +70,6 @@
#include "bd99954-charger.h"
-struct battery_data {
- u16 precharge_current; /* Trickle-charge Current */
- u16 fc_reg_voltage; /* Fast Charging Regulation Voltage */
- u16 voltage_min;
- u16 voltage_max;
-};
-
/* Initial field values, converted to initial register values */
struct bd9995x_init_data {
u16 vsysreg_set; /* VSYS Regulation Setting */
--
2.45.1
next prev parent reply other threads:[~2024-05-28 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 0:06 [PATCH 0/2] power: dead struct removal linux
2024-05-28 0:06 ` linux [this message]
2024-05-28 5:36 ` [PATCH 1/2] power: supply: bd99954: remove unused struct 'battery_data' Matti Vaittinen
2024-05-28 0:06 ` [PATCH 2/2] power: supply: ab8500: remove unused struct 'inst_curr_result_list' linux
2024-05-29 7:47 ` Linus Walleij
2024-06-05 21:38 ` [PATCH 0/2] power: dead struct removal Sebastian Reichel
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=20240528000634.196707-2-linux@treblig.org \
--to=linux@treblig.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=sre@kernel.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).