From: Guenter Roeck <linux@roeck-us.net>
To: Andrew Davis <afd@ti.com>
Cc: Chiang Brian <chiang.brian@inventec.com>,
Erick Karanja <karanja99erick@gmail.com>,
Grant Peltier <grantpeltier93@gmail.com>,
Jeff Lin <jefflin994697@gmail.com>,
Cherrence Sarip <cherrence.sarip@analog.com>,
Kim Seer Paller <kimseer.paller@analog.com>,
Alexis Czezar Torreno <alexisczezar.torreno@analog.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/11] hwmon: (pmbus/bel-pfe) Remove use of i2c_match_id()
Date: Fri, 6 Mar 2026 08:16:37 -0800 [thread overview]
Message-ID: <a39c4e55-ca0f-48cf-a3f5-fe678e23467e@roeck-us.net> (raw)
In-Reply-To: <20260305195642.830695-2-afd@ti.com>
On Thu, Mar 05, 2026 at 01:56:32PM -0600, Andrew Davis wrote:
> The function i2c_match_id() is used to fetch the matching ID from
> the i2c_device_id table. This is often used to then retrieve the
> matching driver_data. This can be done in one step with the helper
> i2c_get_match_data().
>
> This helper has a couple other benefits:
> * It doesn't need the i2c_device_id passed in so we do not need
> to have that forward declared, allowing us to remove those or
> move the i2c_device_id table down to its more natural spot
> with the other module info.
> * It also checks for device match data, which allows for OF and
> ACPI based probing. That means we do not have to manually check
> those first and can remove those checks.
The above seem to be boilerplates, not matching the actual patches.
AI review says:
This isn't a bug, but this description is inaccurate for this specific driver.
Looking at the code before this commit, there were no manual checks for OF or
ACPI match data (like of_match_device or acpi_match_device) in
pfe_pmbus_probe(). The driver only ever relied on i2c_match_id().
Could the commit message be updated to avoid claiming it removes manual
OF/ACPI checks from this specific driver?
Similar feedback applies to most of the patches in this series. Please resend
the series and drop inaccurate information from the commit descriptions.
Thanks,
Guenter
>
> Signed-off-by: Andrew Davis <afd@ti.com>
> ---
> drivers/hwmon/pmbus/bel-pfe.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/drivers/hwmon/pmbus/bel-pfe.c b/drivers/hwmon/pmbus/bel-pfe.c
> index ddf9d9a2958c4..6499556f735b4 100644
> --- a/drivers/hwmon/pmbus/bel-pfe.c
> +++ b/drivers/hwmon/pmbus/bel-pfe.c
> @@ -88,13 +88,10 @@ static struct pmbus_driver_info pfe_driver_info[] = {
> },
> };
>
> -static const struct i2c_device_id pfe_device_id[];
> -
> static int pfe_pmbus_probe(struct i2c_client *client)
> {
> - int model;
> + int model = (uintptr_t)i2c_get_match_data(client);
>
> - model = (int)i2c_match_id(pfe_device_id, client)->driver_data;
> client->dev.platform_data = &pfe_plat_data;
>
> /*
> --
> 2.39.2
>
next prev parent reply other threads:[~2026-03-06 16:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 19:56 [PATCH 00/11] Remove use of i2c_match_id in PMBUS Andrew Davis
2026-03-05 19:56 ` [PATCH 01/11] hwmon: (pmbus/bel-pfe) Remove use of i2c_match_id() Andrew Davis
2026-03-06 16:16 ` Guenter Roeck [this message]
2026-03-06 16:33 ` Andrew Davis
2026-03-05 19:56 ` [PATCH 02/11] hwmon: (pmbus/ibm-cffps) " Andrew Davis
2026-03-06 16:19 ` Guenter Roeck
2026-03-06 17:12 ` Andrew Davis
2026-03-05 19:56 ` [PATCH 03/11] hwmon: (pmbus/isl68137) " Andrew Davis
2026-03-05 19:56 ` [PATCH 04/11] hwmon: (pmbus/max20730) " Andrew Davis
2026-03-05 19:56 ` [PATCH 05/11] hwmon: (pmbus/max34440) " Andrew Davis
2026-03-05 19:56 ` [PATCH 06/11] hwmon: (pmbus) " Andrew Davis
2026-03-05 19:56 ` [PATCH 07/11] hwmon: (pmbus/q54sj108a2) " Andrew Davis
2026-03-05 19:56 ` [PATCH 08/11] hwmon: (pmbus/tps53679) " Andrew Davis
2026-03-06 16:26 ` Guenter Roeck
2026-03-05 19:56 ` [PATCH 09/11] hwmon: (pmbus/fsp-3y) " Andrew Davis
2026-03-05 19:56 ` [PATCH 10/11] hwmon: (pmbus/ltc2978) " Andrew Davis
2026-03-05 19:56 ` [PATCH 11/11] hwmon: (pmbus/max16601) " Andrew Davis
2026-03-06 16:22 ` Guenter Roeck
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=a39c4e55-ca0f-48cf-a3f5-fe678e23467e@roeck-us.net \
--to=linux@roeck-us.net \
--cc=afd@ti.com \
--cc=alexisczezar.torreno@analog.com \
--cc=cherrence.sarip@analog.com \
--cc=chiang.brian@inventec.com \
--cc=grantpeltier93@gmail.com \
--cc=jefflin994697@gmail.com \
--cc=karanja99erick@gmail.com \
--cc=kimseer.paller@analog.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®