Linux I2C development
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Brigham Campbell <me@brighamcampbell.com>
Cc: "Gero Schwäricke" <gero.schwaericke@sevenlab.de>,
	"Jean Delvare" <jdelvare@suse.de>,
	linux-i2c@vger.kernel.org
Subject: Re: [PATCH v2] i2c-tools: Allow passing device file paths
Date: Fri, 29 May 2026 21:58:04 +0200	[thread overview]
Message-ID: <ahnvzEQyKqWfXyrS@shikoro> (raw)
In-Reply-To: <DIT8HHYY12ME.3IGXT8OU1CGZ8@brighamcampbell.com>

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

Hi Brigham, Gero,

> I had worried that doing the device path lookup and opening in one go
> would be overly invasive. Of course, if I can make that work, then it
> would address the concerns that I brought up in my previous email. It
> may be worth the extra effort to avoid the ugly variant struct I
> introduced in this v2.
> 
> I'll take a look at libgpio. Thanks.

I think I agree with Gero here and that it is worth getting rid of the
variant struct.

> This makes sense. In the strange (but totally plausible) case of
> conflicts between bus number, bus name, and bus file/symlink path, the
> order of precedence should be as follows to maintain backwards
> compatibility:
> 
> bus number -> bus name -> bus device path
> 
> I'll fix this in the next revision.

Sounds good!

Looking forward to v3, happy hacking!

   Wolfram


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

      reply	other threads:[~2026-05-29 19:58 UTC|newest]

Thread overview: 5+ 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
2026-04-28 11:43 ` Gero Schwäricke
2026-05-27  6:09   ` Brigham Campbell
2026-05-29 19:58     ` 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=ahnvzEQyKqWfXyrS@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