From: Heiner Kallweit <hkallweit1@gmail.com>
To: jim.cromie@gmail.com
Cc: Wolfram Sang <wsa@kernel.org>,
linux-i2c@vger.kernel.org, Andi Shyti <andi.shyti@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 10/10] i2c: scx200_acb: Don't let i2c adapters declare I2C_CLASS_SPD support if they support I2C_CLASS_HWMON
Date: Sun, 26 Nov 2023 13:18:52 +0100 [thread overview]
Message-ID: <aa9b9945-aba4-4cb1-8089-3f572f00df9b@gmail.com> (raw)
In-Reply-To: <CAJfuBxw4=Aku32yx3e0zbTCARSo9r1ST71UoaC-Dp3K3_m44jQ@mail.gmail.com>
On 26.11.2023 07:03, jim.cromie@gmail.com wrote:
> On Fri, Nov 24, 2023 at 3:16 AM Heiner Kallweit <hkallweit1@gmail.com> wrote:
>>
>> 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>
>>
>
> Acked:
>
Thanks. Could you please respond with a proper Acked-by tag so that patchwork
can pick it up?
>
>> ---
>> drivers/i2c/busses/scx200_acb.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/i2c/busses/scx200_acb.c b/drivers/i2c/busses/scx200_acb.c
>> index 83c1db610..3648382b8 100644
>> --- a/drivers/i2c/busses/scx200_acb.c
>> +++ b/drivers/i2c/busses/scx200_acb.c
>> @@ -427,7 +427,7 @@ static struct scx200_acb_iface *scx200_create_iface(const char *text,
>> snprintf(adapter->name, sizeof(adapter->name), "%s ACB%d", text, index);
>> adapter->owner = THIS_MODULE;
>> adapter->algo = &scx200_acb_algorithm;
>> - adapter->class = I2C_CLASS_HWMON | I2C_CLASS_SPD;
>> + adapter->class = I2C_CLASS_HWMON;
>> adapter->dev.parent = dev;
>>
>> mutex_init(&iface->mutex);
>>
next prev parent reply other threads:[~2023-11-26 12:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 10:16 [PATCH v2 00/10] Don't let i2c adapters declare I2C_CLASS_SPD support if they support I2C_CLASS_HWMON Heiner Kallweit
2023-11-24 10:16 ` [PATCH v2 01/10] i2c: " Heiner Kallweit
2023-11-26 14:21 ` Andi Shyti
2023-11-24 10:16 ` [PATCH v2 02/10] staging: greybus: " Heiner Kallweit
2023-11-24 10:16 ` [PATCH v2 03/10] i2c: pasemi: " Heiner Kallweit
2023-11-26 14:22 ` Andi Shyti
2023-11-24 10:16 ` [PATCH v2 04/10] i2c: " Heiner Kallweit
2023-11-26 14:23 ` Andi Shyti
2023-11-24 10:16 ` [PATCH v2 05/10] i2c: stub: " Heiner Kallweit
2023-11-24 10:16 ` [PATCH v2 06/10] i2c: gpio: " Heiner Kallweit
2023-11-26 14:24 ` Andi Shyti
2023-11-24 10:16 ` [PATCH v2 07/10] i2c: mlxcpld: " Heiner Kallweit
2023-11-26 14:24 ` Andi Shyti
2023-11-24 10:16 ` [PATCH v2 08/10] media: netup_unidvb: " Heiner Kallweit
2023-12-05 8:13 ` Hans Verkuil
2023-11-24 10:16 ` [PATCH v2 09/10] i2c: ali1563: " Heiner Kallweit
2023-11-26 14:24 ` Andi Shyti
2023-11-24 10:16 ` [PATCH v2 10/10] i2c: scx200_acb: " Heiner Kallweit
2023-11-26 6:03 ` jim.cromie
2023-11-26 12:18 ` Heiner Kallweit [this message]
2023-11-26 14:30 ` Andi Shyti
2023-12-16 20:23 ` [PATCH v2 00/10] " Heiner Kallweit
2023-12-19 12:36 ` Wolfram Sang
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=aa9b9945-aba4-4cb1-8089-3f572f00df9b@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=jim.cromie@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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