From: Heiner Kallweit <hkallweit1@gmail.com>
To: Wolfram Sang <wsa@kernel.org>, Sergey Kozlov <serjk@netup.ru>
Cc: linux-i2c@vger.kernel.org, Heiner Kallweit <hkallweit1@gmail.com>,
Abylay Ospan <aospan@netup.ru>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 08/10] drivers/media/pci/netup_unidvb/netup_unidvb_i2c.c: Don't let i2c adapters declare I2C_CLASS_SPD support if they support I2C_CLASS_HWMON
Date: Sat, 18 Nov 2023 19:05:02 +0100 [thread overview]
Message-ID: <20231118180504.1785-9-hkallweit1@gmail.com> (raw)
In-Reply-To: <20231118180504.1785-1-hkallweit1@gmail.com>
After removal of the legacy eeprom driver the only remaining I2C
client device driver supporting I2C_CLASS_SPD is jc42. Because this
driver also supports I2C_CLASS_HWMON, adapters don't have to
declare support for I2C_CLASS_SPD if they support I2C_CLASS_HWMON.
It's one step towards getting rid of I2C_CLASS_SPD mid-term.
Series was created supported by Coccinelle and its splitpatch.
Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
---
drivers/media/pci/netup_unidvb/netup_unidvb_i2c.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/pci/netup_unidvb/netup_unidvb_i2c.c b/drivers/media/pci/netup_unidvb/netup_unidvb_i2c.c
index bd38ce444..46676f2c8 100644
--- a/drivers/media/pci/netup_unidvb/netup_unidvb_i2c.c
+++ b/drivers/media/pci/netup_unidvb/netup_unidvb_i2c.c
@@ -289,7 +289,7 @@ static const struct i2c_algorithm netup_i2c_algorithm = {
static const struct i2c_adapter netup_i2c_adapter = {
.owner = THIS_MODULE,
.name = NETUP_UNIDVB_NAME,
- .class = I2C_CLASS_HWMON | I2C_CLASS_SPD,
+ .class = I2C_CLASS_HWMON,
.algo = &netup_i2c_algorithm,
};
next prev parent reply other threads:[~2023-11-18 18:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 18:04 [PATCH 00/10] Don't let i2c adapters declare I2C_CLASS_SPD support if they support I2C_CLASS_HWMON Heiner Kallweit
2023-11-18 18:04 ` [PATCH 01/10] drivers/i2c/busses: " Heiner Kallweit
2023-11-23 20:57 ` Wolfram Sang
2023-11-23 21:58 ` Heiner Kallweit
2023-11-18 18:04 ` [PATCH 02/10] drivers/staging/greybus/i2c.c: " Heiner Kallweit
2023-11-23 12:47 ` Greg Kroah-Hartman
2023-11-18 18:04 ` [PATCH 03/10] drivers/i2c/busses/i2c-pasemi-pci.c: " Heiner Kallweit
2023-11-18 18:04 ` [PATCH 04/10] drivers/i2c/i2c-stub.c: " Heiner Kallweit
2023-11-18 18:04 ` [PATCH 05/10] drivers/i2c/busses: " Heiner Kallweit
2023-11-23 23:10 ` Peter Rosin
2023-11-24 10:09 ` Heiner Kallweit
2023-11-18 18:05 ` [PATCH 06/10] drivers/i2c/busses/i2c-gpio.c: " Heiner Kallweit
2023-11-18 18:05 ` [PATCH 07/10] drivers/i2c/busses/i2c-mlxcpld.c: " Heiner Kallweit
2023-11-18 18:05 ` Heiner Kallweit [this message]
2023-11-23 20:55 ` [PATCH 08/10] drivers/media/pci/netup_unidvb/netup_unidvb_i2c.c: " Wolfram Sang
2023-11-24 10:15 ` Heiner Kallweit
2023-11-18 18:05 ` [PATCH 09/10] drivers/i2c/busses/scx200_acb.c: " Heiner Kallweit
2023-11-18 18:05 ` [PATCH 10/10] drivers/i2c/busses/i2c-ali1563.c: " Heiner Kallweit
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=20231118180504.1785-9-hkallweit1@gmail.com \
--to=hkallweit1@gmail.com \
--cc=aospan@netup.ru \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=serjk@netup.ru \
--cc=wsa@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