From: "Brigham Campbell" <me@brighamcampbell.com>
To: "Wolfram Sang" <wsa+renesas@sang-engineering.com>,
"Brigham Campbell" <me@brighamcampbell.com>
Cc: "Jean Delvare" <jdelvare@suse.de>,
linux-i2c@vger.kernel.org,
"Gero Schwäricke" <gero.schwaericke@sevenlab.de>
Subject: Re: [PATCH v5 0/2] i2c-tools: Make tools accept bus path
Date: Sat, 03 Oct 2026 20:57:01 -0600 [thread overview]
Message-ID: <DLVPSTHQJ2F9.1HPIUXJ2EW5RU@brighamcampbell.com> (raw)
In-Reply-To: <ark-AXt29OBT5hbg@ninjato>
On Sun Sep 27, 2026 at 10:02 AM MDT, Wolfram Sang wrote:
> The main problem here is time :( I have important conferences coming up,
> so I can only schedule this to the second half of October, I am afraid.
No worries at all. I understand. I hope you enjoy the conferences!
> What would help a little is maybe a description what cases you tested?
I tested as I was developing the patch, but that was a while ago now.
I'll test some more and report back with the details.
By the way, I'm happy to review (and test, when I can) other patches if
it would help. If so, feel free to send me some lore links or msgids.
--
Brigham Campbell
https://brighamcampbell.com
prev parent reply other threads:[~2026-10-04 2:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 8:52 [PATCH v5 0/2] i2c-tools: Make tools accept bus path Brigham Campbell
2026-07-22 8:52 ` [PATCH v5 1/2] i2c-tools: Allow passing device file paths Brigham Campbell
2026-07-22 8:52 ` [PATCH v5 2/2] i2c-tools: Document device paths as I2CBUS arg Brigham Campbell
2026-09-07 21:18 ` [PATCH v5 0/2] i2c-tools: Make tools accept bus path Brigham Campbell
2026-09-27 16:02 ` Wolfram Sang
2026-10-04 2:57 ` Brigham Campbell [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=DLVPSTHQJ2F9.1HPIUXJ2EW5RU@brighamcampbell.com \
--to=me@brighamcampbell.com \
--cc=gero.schwaericke@sevenlab.de \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.