mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Muchamad Coirul Anwar" <muchamadcoirulanwar@gmail.com>
Cc: "Igor Korotin" <igor.korotin@linux.dev>, <jic23@kernel.org>,
	<lars@metafoo.de>, <linux-iio@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-i2c@vger.kernel.org>,
	<andi.shyti@kernel.org>, <wsa+renesas@sang-engineering.com>,
	<ojeda@kernel.org>, <branstj@gmail.com>
Subject: Re: [RFC PATCH v4 1/3] i2c: rust: implement SMBus read abstraction via kernel::io::Io for I2cClient
Date: Mon, 20 Jul 2026 01:02:34 +0200	[thread overview]
Message-ID: <DK2X7WBPOPWC.TY09ODVGYUVM@kernel.org> (raw)
In-Reply-To: <CAO26r3Ttyfqhs3_jWDFym7FpswqFW4-UA8p1pQBcuWzDGGzstg@mail.gmail.com>

On Tue Jul 14, 2026 at 6:08 PM CEST, Muchamad Coirul Anwar wrote:
> Agreed. I will rework on top of Danilo's FallibleIoCapable approach
> in v5. I checked rust-next and neither FallibleIoCapable nor
> io_projection v6 has landed yet.

The patch series is merged in driver-core-next [1]. You can check the
MAINTAINERS file to see how patches for certain subsystems, components and
drivers are usually routed.

If unsure you can also check the linux-next integration tree [2] which merges
all development trees in a daily effort.

> Danilo, should I wait for io_projection to land first before rebasing,
> or should I carry FallibleIoCapable as a preparatory patch in my series?

As mentioned, I/O projections did land already. Regarding the FallibleIoCapable
change, please feel free to pick up the diff I posted and send it as a
prerequisite patch in your series.

Thanks,
Danilo

[1] https://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git/log/?h=driver-core-next
[2] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/

  parent reply	other threads:[~2026-07-19 23:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 15:15 [RFC PATCH v4 0/3] iio: position: add Rust driver for ams AS5600 Muchamad Coirul Anwar
2026-07-07 15:15 ` [RFC PATCH v4 1/3] i2c: rust: implement SMBus read abstraction via kernel::io::Io for I2cClient Muchamad Coirul Anwar
2026-07-11 10:05   ` Igor Korotin
2026-07-11 12:05     ` Danilo Krummrich
2026-07-14 16:08     ` Muchamad Coirul Anwar
2026-07-18  2:48       ` Bruce Robertson
2026-07-19 15:40         ` Muchamad Coirul Anwar
2026-07-19 23:02       ` Danilo Krummrich [this message]
2026-07-20  2:26         ` Muchamad Coirul Anwar
2026-07-11 12:08   ` Danilo Krummrich
2026-07-14 16:10     ` Muchamad Coirul Anwar
2026-07-07 15:15 ` [RFC PATCH v4 2/3] rust: add minimal IIO subsystem abstractions Muchamad Coirul Anwar
2026-07-11 12:12   ` Danilo Krummrich
2026-07-14 16:20     ` Muchamad Coirul Anwar
2026-07-07 15:15 ` [RFC PATCH v4 3/3] iio: position: add Rust driver for ams AS5600 Muchamad Coirul Anwar
2026-07-08 10:36 ` [RFC PATCH v4 0/3] " Miguel Ojeda
2026-07-08 12:37   ` 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=DK2X7WBPOPWC.TY09ODVGYUVM@kernel.org \
    --to=dakr@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=branstj@gmail.com \
    --cc=igor.korotin@linux.dev \
    --cc=jic23@kernel.org \
    --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=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

Powered by JetHome