From: sashiko-bot@kernel.org
To: "Ariana Lazar" <ariana.lazar@microchip.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 4/9] iio: dac: mcp47feb02: use dev_dbg for invalid label
Date: Wed, 19 Aug 2026 12:49:59 +0000 [thread overview]
Message-ID: <20260819125000.6DE0E1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260819-mcp47feb02_refactor-v4-4-beb2aa3bfd09@microchip.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Making the label property optional causes the `label` sysfs attribute to return the literal string `(null)` for channels without a label.
--
--- Patch [4]: [PATCH v4 4/9] iio: dac: mcp47feb02: use dev_dbg for invalid label ---
commit 60f7652ad06abf540ec40667fe14b057bf9a477b
Author: Ariana Lazar <ariana.lazar@microchip.com>
iio: dac: mcp47feb02: use dev_dbg for invalid label
This commit modifies the firmware parsing logic to tolerate missing or
invalid label properties. Instead of aborting the probe with an error, it
logs a debug message and continues initialization.
> diff --git a/drivers/iio/dac/mcp47feb02.c b/drivers/iio/dac/mcp47feb02.c
> index 2ee981393aa1a..e5533fa3c31c0 100644
> --- a/drivers/iio/dac/mcp47feb02.c
> +++ b/drivers/iio/dac/mcp47feb02.c
[ ... ]
> @@ -978,8 +979,7 @@ static int mcp47feb02_parse_fw(struct iio_dev *indio_dev,
>
> ret = fwnode_property_read_string(child, "label", &data->labels[reg]);
> if (ret)
> - return dev_err_probe(dev, ret, "%pfw: invalid label\n",
> - fwnode_get_name(child));
> + dev_dbg(dev, "%s: invalid label\n", fwnode_get_name(child));
[Severity: Medium]
When the label property is invalid or missing, data->labels[reg] will
now remain NULL.
Because the IIO core still registers the label sysfs attribute when
the read_label callback is populated, could this introduce a regression
where mcp47feb02_read_label() outputs the literal string "(null)"?
drivers/iio/dac/mcp47feb02.c:mcp47feb02_read_label() {
struct mcp47feb02_data *data = iio_priv(indio_dev);
return sysfs_emit(label, "%s\n", data->labels[ch->address]);
}
Since sysfs_emit() unconditionally formats a NULL pointer as "(null)",
userspace tools might parse "(null)" as the channel's actual label. Should
mcp47feb02_read_label() handle the NULL case and return an error code like
-ENOENT instead?
>
> chanspec.address = reg;
> chanspec.channel = reg;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260819-mcp47feb02_refactor-v4-0-beb2aa3bfd09@microchip.com?part=4
next prev parent reply other threads:[~2026-08-19 12:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 12:41 [PATCH v4 0/9] Refactor Microchip MCP47FEB02 I2C driver in separate modules to add support for MCP48FEB02 SPI driver Ariana Lazar
2026-08-19 12:41 ` [PATCH v4 1/9] iio: dac: mcp47feb02: initialize dac_data field in channel data struct at probe Ariana Lazar
2026-08-19 14:17 ` Andy Shevchenko
2026-08-19 12:41 ` [PATCH v4 2/9] iio: dac: mcp47feb02: correct gain bitshift " Ariana Lazar
2026-08-19 12:50 ` sashiko-bot
2026-08-19 14:15 ` Andy Shevchenko
2026-08-19 12:41 ` [PATCH v4 3/9] iio: dac: mcp47feb02: correct false state case in store_eeprom_store Ariana Lazar
2026-08-19 12:51 ` sashiko-bot
2026-08-19 14:18 ` Andy Shevchenko
2026-08-19 12:41 ` [PATCH v4 4/9] iio: dac: mcp47feb02: use dev_dbg for invalid label Ariana Lazar
2026-08-19 12:49 ` sashiko-bot [this message]
2026-08-19 14:23 ` Andy Shevchenko
2026-08-19 12:41 ` [PATCH v4 5/9] iio: dac: mcp47feb02: correct typo from a comment Ariana Lazar
2026-08-19 12:41 ` [PATCH v4 6/9] iio: dac: mcp47feb02: rename command mask define Ariana Lazar
2026-08-19 12:46 ` sashiko-bot
2026-08-19 12:41 ` [PATCH v4 7/9] iio: dac: mcp47feb02: refactor MCP47FEB02 I2C driver into two modules Ariana Lazar
2026-08-19 12:52 ` sashiko-bot
2026-08-19 12:41 ` [PATCH v4 8/9] dt-bindings: iio: dac: add support for MCP48FEB02 SPI Ariana Lazar
2026-08-19 12:41 ` [PATCH v4 9/9] iio: dac: add support for Microchip MCP48FEB02 Ariana Lazar
2026-08-19 12:53 ` sashiko-bot
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=20260819125000.6DE0E1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=ariana.lazar@microchip.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@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