From: sashiko-bot@kernel.org
To: "Abdurrahman Hussain via B4 Relay"
<devnull+abdurrahman.nexthop.ai@kernel.org>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v2 5/5] hwmon: (pmbus/adm1266) include adapter number in GPIO line label
Date: Tue, 12 May 2026 01:31:41 +0000 [thread overview]
Message-ID: <20260512013141.D6890C2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260510-adm1266-v2-5-3a22b903c2f1@nexthop.ai>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Critical] Changing the generated GPIO line names breaks backwards compatibility for userspace tools and scripts.
--
commit c155c76ac978e1fe6990333ff1cb0db4a1c40a1e
Author: Abdurrahman Hussain <abdurrahman@nexthop.ai>
hwmon: (pmbus/adm1266) include adapter number in GPIO line label
This commit updates the GPIO line labels for the ADM1266 driver to include
the I2C adapter number, in addition to the slave address. This is intended
to disambiguate labels when multiple devices use the same 7-bit address on
different buses.
> The label is purely informational (visible via gpioinfo and the
> gpiochip /sys/class/gpio name); no DT or ABI consumer parses it.
Does changing the generated GPIO line names risk breaking backwards
compatibility for userspace tools and scripts?
These names are exposed to userspace via the GPIO chardev API and sysfs, and
userspace tools (such as libgpiod) or custom scripts can request GPIO lines
by their names. Modifying these names might break existing userspace
deployments that rely on the old naming convention.
> diff --git a/drivers/hwmon/pmbus/adm1266.c b/drivers/hwmon/pmbus/adm1266.c
> index 0dfb02db86837..479e768ff87ca 100644
> --- a/drivers/hwmon/pmbus/adm1266.c
> +++ b/drivers/hwmon/pmbus/adm1266.c
> @@ -292,8 +292,9 @@ static int adm1266_config_gpio(struct adm1266_data *data)
> int i;
>
> for (i = 0; i < ARRAY_SIZE(data->gpio_names); i++) {
> - gpio_name = devm_kasprintf(&data->client->dev, GFP_KERNEL, "adm1266-%x-%s",
> - data->client->addr, adm1266_names[i]);
> + gpio_name = devm_kasprintf(&data->client->dev, GFP_KERNEL, "adm1266-%d-%x-%s",
> + data->client->adapter->nr, data->client->addr,
> + adm1266_names[i]);
Could this naming format change cause regressions for userspace applications
that are already matching on the previous adm1266-%x-%s format?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260510-adm1266-v2-0-3a22b903c2f1@nexthop.ai?part=5
prev parent reply other threads:[~2026-05-12 1:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 4:48 [PATCH v2 0/5] hwmon: (pmbus/adm1266) blackbox, FW rev, rtc_class, GPIO label Abdurrahman Hussain via B4 Relay
2026-05-11 4:48 ` [PATCH v2 1/5] hwmon: (pmbus/adm1266) add firmware_revision debugfs entry Abdurrahman Hussain via B4 Relay
2026-05-11 4:48 ` [PATCH v2 2/5] hwmon: (pmbus/adm1266) add clear_blackbox " Abdurrahman Hussain via B4 Relay
2026-05-12 0:03 ` sashiko-bot
2026-05-11 4:48 ` [PATCH v2 3/5] hwmon: (pmbus/adm1266) add powerup_counter " Abdurrahman Hussain via B4 Relay
2026-05-12 0:34 ` sashiko-bot
2026-05-11 4:48 ` [PATCH v2 4/5] hwmon: (pmbus/adm1266) replace probe-time RTC seed with rtc_class device Abdurrahman Hussain via B4 Relay
2026-05-12 1:12 ` sashiko-bot
2026-05-11 4:48 ` [PATCH v2 5/5] hwmon: (pmbus/adm1266) include adapter number in GPIO line label Abdurrahman Hussain via B4 Relay
2026-05-12 1:31 ` sashiko-bot [this message]
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=20260512013141.D6890C2BCB0@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=devnull+abdurrahman.nexthop.ai@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=sashiko@lists.linux.dev \
/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