From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Igor Korotin <igor.korotin@linux.dev>, rust-for-linux@vger.kernel.org
Cc: Wolfram Sang <wsa@kernel.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Danilo Krummrich <dakr@kernel.org>
Subject: Re: [GIT PULL] rust-i2c-fixes for 7.1-rc7
Date: Tue, 9 Jun 2026 11:26:40 +0200 [thread overview]
Message-ID: <aifcUBtuker3f9t2@shikoro> (raw)
In-Reply-To: <aiZ0eD-A2F8woqTb@shikoro>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
Hi all,
(adding a few more people to CC to have a potentially bigger discussion)
> Please be already aware that from 7.2 on, you will need send pull
> requests to Andi who takes over the I2C subsystem. I will write a
> seperate mail about the handover later today.
Done now [1]. On a second thought, after pulling in the I2C abstractions
a few times now, I wonder meanwhile if the Rust-tree wouldn't be the
better path to upstream. The abstractions are way more Rust than they
are I2C. And potential merge-conflicts come from generic Rust
abstraction updates, not from I2C.
This is Andi's choice now, of course. Just wanted to give my 2 cents
here...
Happy hacking,
Wolfram
[1] https://lore.kernel.org/r/20260609091612.8228-3-wsa+renesas@sang-engineering.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-06-09 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 17:39 [GIT PULL] rust-i2c-fixes for 7.1-rc7 Igor Korotin
2026-06-08 7:51 ` Wolfram Sang
2026-06-09 9:26 ` Wolfram Sang [this message]
2026-06-09 12:08 ` Igor Korotin
2026-06-09 14:53 ` Miguel Ojeda
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=aifcUBtuker3f9t2@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=dakr@kernel.org \
--cc=igor.korotin@linux.dev \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=wsa@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.