From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: "Gero Schwäricke" <gero.schwaericke@sevenlab.de>
Cc: Brigham Campbell <me@brighamcampbell.com>,
Jean Delvare <jdelvare@suse.de>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v4 1/2] i2c-tools: Allow passing device file paths
Date: Mon, 13 Jul 2026 17:06:03 +0200 [thread overview]
Message-ID: <alT-251aiK7B0ViQ@shikoro> (raw)
In-Reply-To: <DJXC1KBY7IXJ.32N5ILIXL8J4N@sevenlab.de>
[-- Attachment #1: Type: text/plain, Size: 564 bytes --]
Hi Gero,
> they have non-unique I2C bus names which uses i2cdump and evaluates
> stderr for the string
I get your point. I'd argue that relying on error strings is very thin
ice, as they are not an API. I think error messages are going to change
with this patch set anyhow. Probably for the better, if done right. I'd
suggest to continue with the series based on our feedback and see how we
end up with the error reporting in a user friendly way. Maybe we can
even use better return values to help scripts? We will see...
D'accord?
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-07-13 15:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 4:27 [PATCH v4 0/2] i2c-tools: Make tools accept bus path Brigham Campbell
2026-07-06 4:27 ` [PATCH v4 1/2] i2c-tools: Allow passing device file paths Brigham Campbell
2026-07-09 12:18 ` Wolfram Sang
2026-07-09 12:40 ` Gero Schwäricke
2026-07-11 19:24 ` Wolfram Sang
2026-07-13 9:23 ` Gero Schwäricke
2026-07-13 15:06 ` Wolfram Sang [this message]
2026-07-14 9:30 ` Gero Schwäricke
2026-07-14 10:13 ` Wolfram Sang
2026-07-13 9:37 ` Gero Schwäricke
2026-07-13 15:38 ` Brigham Campbell
2026-07-14 9:42 ` Gero Schwäricke
2026-07-06 4:27 ` [PATCH v4 2/2] i2c-tools: Document device paths as I2CBUS arg Brigham Campbell
2026-07-11 19:43 ` 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=alT-251aiK7B0ViQ@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=gero.schwaericke@sevenlab.de \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=me@brighamcampbell.com \
/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