From: Heiner Kallweit <hkallweit1@gmail.com>
To: Andi Shyti <andi.shyti@kernel.org>,
Jean Delvare <jdelvare@suse.com>,
Wolfram Sang <wsa@the-dreams.de>,
Peter Korsgaard <peter.korsgaard@barco.com>,
Peter Rosin <peda@axentia.se>, Guenter Roeck <linux@roeck-us.net>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>
Subject: [PATCH 3/4] hwmon: jc42: Remove I2C_CLASS_SPD support
Date: Mon, 15 Apr 2024 22:49:35 +0200 [thread overview]
Message-ID: <3c4a1715-bfbb-4ae2-b35f-2f20f95e4932@gmail.com> (raw)
In-Reply-To: <90a0786f-136b-4097-9def-8d52e9e5d3cc@gmail.com>
Last host driver supporting I2C_CLASS_SPD was i801. Now that I2C_CLASS_SPD
support has been removed there, we can remove it here too.
Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
---
drivers/hwmon/jc42.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwmon/jc42.c b/drivers/hwmon/jc42.c
index 75dc25df0..a00168fe5 100644
--- a/drivers/hwmon/jc42.c
+++ b/drivers/hwmon/jc42.c
@@ -623,7 +623,7 @@ MODULE_DEVICE_TABLE(of, jc42_of_ids);
#endif
static struct i2c_driver jc42_driver = {
- .class = I2C_CLASS_SPD | I2C_CLASS_HWMON,
+ .class = I2C_CLASS_HWMON,
.driver = {
.name = "jc42",
.pm = JC42_DEV_PM_OPS,
--
2.44.0
next prev parent reply other threads:[~2024-04-15 20:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 20:47 [PATCH 0/4] i2c: Remove I2C_CLASS_SPD Heiner Kallweit
2024-04-15 20:47 ` [PATCH 1/4] i2c: i801: Remove usage of I2C_CLASS_SPD Heiner Kallweit
2024-04-15 20:48 ` [PATCH 2/4] i2c: mux: gpio: remove support for class-based device instantiation Heiner Kallweit
2024-04-15 20:49 ` Heiner Kallweit [this message]
2024-04-15 21:43 ` [PATCH 3/4] hwmon: jc42: Remove I2C_CLASS_SPD support Guenter Roeck
2024-04-15 20:50 ` [PATCH 4/4] i2c: Remove I2C_CLASS_SPD Heiner Kallweit
2024-04-17 8:05 ` Andi Shyti
2024-04-17 10:27 ` Heiner Kallweit
2024-04-16 22:46 ` (subset) [PATCH 0/4] " Andi Shyti
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=3c4a1715-bfbb-4ae2-b35f-2f20f95e4932@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=peda@axentia.se \
--cc=peter.korsgaard@barco.com \
--cc=wsa@the-dreams.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).