From: Jonathan Cameron <jic23@kernel.org>
To: Muchamad Coirul Anwar <muchamadcoirulanwar@gmail.com>
Cc: Mark Brown <broonie@kernel.org>,
lars@metafoo.de, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
rust-for-linux@vger.kernel.org, andi.shyti@kernel.org,
wsa+renesas@sang-engineering.com, ojeda@kernel.org,
dakr@kernel.org, igor.korotin@linux.dev, branstj@gmail.com,
brucer42@gmail.com
Subject: Re: [RFC PATCH v5 1/3] i2c: rust: implement SMBus access via IoBackend and FallibleIoCapable
Date: Tue, 1 Sep 2026 02:10:54 +0100 [thread overview]
Message-ID: <20260901021054.057aab97@jic23-huawei> (raw)
In-Reply-To: <CAO26r3QwUZ1QeO3PYNPoYQrbKpzfhttYAi0kNNB+QumAN=vZkQ@mail.gmail.com>
> > > +impl I2cClient<device::Bound> {
> > > + /// Returns an I/O handle for SMBus register access on this I2C client.
> > > + ///
> > > + /// The returned handle provides fallible read/write methods for the
> > > + /// 256-byte SMBus command address space (0x00–0xFF). This is the SMBus
> > > + /// command byte range, NOT the 7-bit device address, which is handled
> > > + /// by the I2C core at the adapter level.
> >
> > That rather feels like you are correcting my confusion in the earlier version!
> > I'd assume people are more awake than me and skip the NOT part ;)
>
> Sorry for the tone. I didn't mean to correct you. I'll drop that line.
No problem. It wasn't the tone (which was fine!) - just the excess detail.
So dropping it works for me!
Jonathan
next prev parent reply other threads:[~2026-09-01 1:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 6:26 [RFC PATCH v5 0/3] iio: position: add Rust driver for ams AS5600 Muchamad Coirul Anwar
2026-08-22 6:26 ` [RFC PATCH v5 1/3] i2c: rust: implement SMBus access via IoBackend and FallibleIoCapable Muchamad Coirul Anwar
2026-08-23 23:41 ` Jonathan Cameron
2026-08-28 6:10 ` Muchamad Coirul Anwar
2026-09-01 1:10 ` Jonathan Cameron [this message]
2026-08-22 6:26 ` [RFC PATCH v5 2/3] rust: add minimal IIO subsystem abstractions Muchamad Coirul Anwar
2026-08-24 0:07 ` Jonathan Cameron
2026-08-28 6:53 ` Muchamad Coirul Anwar
2026-09-01 1:14 ` Jonathan Cameron
2026-09-02 5:05 ` Muchamad Coirul Anwar
2026-08-22 6:26 ` [RFC PATCH v5 3/3] iio: position: add Rust driver for ams AS5600 Muchamad Coirul Anwar
2026-08-24 0:17 ` Jonathan Cameron
2026-08-28 7:01 ` Muchamad Coirul Anwar
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=20260901021054.057aab97@jic23-huawei \
--to=jic23@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=branstj@gmail.com \
--cc=broonie@kernel.org \
--cc=brucer42@gmail.com \
--cc=dakr@kernel.org \
--cc=igor.korotin@linux.dev \
--cc=lars@metafoo.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=muchamadcoirulanwar@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@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