Linux I2C development
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: 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: Mon, 16 Nov 2026 09:04:22 +0100	[thread overview]
Message-ID: <avq5BubiO_KtXg_F@shikoro> (raw)
In-Reply-To: <20260722-accept-device-path-v5-0-9c0bf9b4da26@brighamcampbell.com>

[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]

On Wed, Jul 22, 2026 at 02:52:39AM -0600, 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.
> 
> Since v1:
>  * Scrapped brittle checking against device major number 89 in favor of
>    an i2c_bus_hint variant struct.
> Since v2:
>  * Scrapped i2c_bus_hint variant in favor of combining the lookup and
>    open steps into one function. No more awkward variant.
> Since v3:
>  * Rebased onto `master` and fixed minor conflicts.
> Since v4:
>  * Inline much of the functionality of open_i2c_dev.
>  * Where possible, make functions static.
> 
> Signed-off-by: Brigham Campbell <me@brighamcampbell.com>
> ---
> Brigham Campbell (2):
>       i2c-tools: Allow passing device file paths
>       i2c-tools: Document device paths as I2CBUS arg

Applied, thank you!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2026-11-16  8:04 UTC|newest]

Thread overview: 11+ 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-11-08 13:09   ` Wolfram Sang
2026-11-15 22:34     ` Wolfram Sang
2026-11-16  7:23     ` Brigham Campbell
2026-11-16  8:00       ` Wolfram Sang
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
2026-11-16  8:04 ` Wolfram Sang [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=avq5BubiO_KtXg_F@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