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
Subject: Re: [PATCH v4 2/2] i2c-tools: Document device paths as I2CBUS arg
Date: Sat, 11 Jul 2026 21:43:58 +0200	[thread overview]
Message-ID: <alKc_hwhYmFue-bs@shikoro> (raw)
In-Reply-To: <20260705-accept-device-path-v4-2-c62caa708a9e@brighamcampbell.com>

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

On Sun, Jul 05, 2026 at 10:27:54PM -0600, Brigham Campbell wrote:
> i2c-tools now accept device file paths in addition to the i2c adapter
> number and i2c adapter name. Add this capability to documentation.
> 
> Signed-off-by: Brigham Campbell <me@brighamcampbell.com>

Looks okay to me. Thank you!


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

      reply	other threads:[~2026-07-11 19:44 UTC|newest]

Thread overview: 18+ 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
2026-07-14  9:30           ` Gero Schwäricke
2026-07-14 10:13             ` Wolfram Sang
2026-07-16 14:49     ` Brigham Campbell
2026-07-17 13:00       ` Gero Schwäricke
2026-07-19 22:22         ` Brigham Campbell
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-16 14:17         ` Brigham Campbell
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 [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=alKc_hwhYmFue-bs@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --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