From: linux@treblig.org
To: jic23@kernel.org, lars@metafoo.de, marius.cristea@microchip.com,
mazziesaccount@gmail.com
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Dr. David Alan Gilbert" <linux@treblig.org>
Subject: [PATCH 3/3] iio: light: rohm-bu27034: remove unused struct 'bu27034_result'
Date: Thu, 23 May 2024 00:04:57 +0100 [thread overview]
Message-ID: <20240522230457.478156-4-linux@treblig.org> (raw)
In-Reply-To: <20240522230457.478156-1-linux@treblig.org>
From: "Dr. David Alan Gilbert" <linux@treblig.org>
'bu27034_result' is unused since the original
commit e52afbd61039 ("iio: light: ROHM BU27034 Ambient Light Sensor").
Remove it.
Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
---
drivers/iio/light/rohm-bu27034.c | 6 ------
1 file changed, 6 deletions(-)
diff --git a/drivers/iio/light/rohm-bu27034.c b/drivers/iio/light/rohm-bu27034.c
index bf3de853a811..4937bf6fa046 100644
--- a/drivers/iio/light/rohm-bu27034.c
+++ b/drivers/iio/light/rohm-bu27034.c
@@ -223,12 +223,6 @@ struct bu27034_data {
} scan;
};
-struct bu27034_result {
- u16 ch0;
- u16 ch1;
- u16 ch2;
-};
-
static const struct regmap_range bu27034_volatile_ranges[] = {
{
.range_min = BU27034_REG_SYSTEM_CONTROL,
--
2.45.1
next prev parent reply other threads:[~2024-05-22 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 23:04 [PATCH 0/3] IIO dead struct cleanup linux
2024-05-22 23:04 ` [PATCH 1/3] iio: accel: bmi088: remove unused struct 'bmi088_scale_info' linux
2024-05-22 23:04 ` [PATCH 2/3] iio: adc: pac1934: remove unused struct 'samp_rate_mapping' linux
2024-05-22 23:04 ` linux [this message]
2024-05-23 5:50 ` [PATCH 3/3] iio: light: rohm-bu27034: remove unused struct 'bu27034_result' Matti Vaittinen
2024-05-25 16:41 ` [PATCH 0/3] IIO dead struct cleanup Jonathan Cameron
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=20240522230457.478156-4-linux@treblig.org \
--to=linux@treblig.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marius.cristea@microchip.com \
--cc=mazziesaccount@gmail.com \
/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