Linux I2C development
 help / color / mirror / Atom feed
From: "Brigham Campbell" <me@brighamcampbell.com>
To: "Brigham Campbell" <me@brighamcampbell.com>,
	"Jean Delvare" <jdelvare@suse.de>, <linux-i2c@vger.kernel.org>,
	"Wolfram Sang" <wsa+renesas@sang-engineering.com>
Cc: "Gero Schwäricke" <gero.schwaericke@sevenlab.de>
Subject: Re: [PATCH v5 0/2] i2c-tools: Make tools accept bus path
Date: Mon, 07 Sep 2026 15:18:07 -0600	[thread overview]
Message-ID: <DL9EB60C2IIA.228Z11CQM65Q3@brighamcampbell.com> (raw)
In-Reply-To: <20260722-accept-device-path-v5-0-9c0bf9b4da26@brighamcampbell.com>

Hi, Wolfram, Jean!

On Wed Jul 22, 2026 at 2:52 AM MDT, Brigham Campbell wrote:
> The purpose of this series is to make i2c-tools userspace utilities
> accept an i2c bus character device file path as an argument. This is
> useful, for example, if a sysadmin creates udev rules to create a
> persistent symlink to an i2c bus and wishes to use that symlink with
> i2c-tools.

I appreciate the feedback you've given to help get this series to v5. Do
you have any outstanding concerns about this series? Is there anything I
can do to help get it across the finish line?

Thanks!
-- 
Brigham Campbell
https://brighamcampbell.com


      parent reply	other threads:[~2026-09-07 21:18 UTC|newest]

Thread overview: 4+ 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 ` 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=DL9EB60C2IIA.228Z11CQM65Q3@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