From: "Brigham Campbell" <me@brighamcampbell.com>
To: "Brigham Campbell" <me@brighamcampbell.com>,
"Jean Delvare" <jdelvare@suse.de>, <linux-i2c@vger.kernel.org>
Cc: "Wolfram Sang" <wsa+renesas@sang-engineering.com>,
"Gero Schwäricke" <gero.schwaericke@sevenlab.de>
Subject: Re: [PATCH v2] i2c-tools: Allow passing device file paths
Date: Wed, 01 Apr 2026 17:33:21 -0600 [thread overview]
Message-ID: <DHI7M3AVM0JL.C8F5I19CRT2P@brighamcampbell.com> (raw)
In-Reply-To: <20260312081808.347978-1-me@brighamcampbell.com>
Jean, Wolfram,
Have either of you had the opportunity to review these changes?
In hindsight, I should have split it into one patch to the code and
another to the documentation. If you'd like me to split it up for easier
reviewal and send out a v3, please let me know.
Thanks,
Brigham
next prev parent reply other threads:[~2026-04-01 23:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 8:18 [PATCH v2] i2c-tools: Allow passing device file paths Brigham Campbell
2026-04-01 23:33 ` Brigham Campbell [this message]
2026-04-28 11:43 ` Gero Schwäricke
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=DHI7M3AVM0JL.C8F5I19CRT2P@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox