* Re: [GIT PULL] rust-i2c-fixes for 7.1-rc7
[not found] ` <aiZ0eD-A2F8woqTb@shikoro>
@ 2026-06-09 9:26 ` Wolfram Sang
0 siblings, 0 replies; only message in thread
From: Wolfram Sang @ 2026-06-09 9:26 UTC (permalink / raw)
To: Igor Korotin, rust-for-linux
Cc: Wolfram Sang, linux-i2c, linux-kernel, Danilo Krummrich
[-- 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 --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-06-09 9:26 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <9e49b71b-8b60-479e-93e7-5c12e352c78e@linux.dev>
[not found] ` <aiZ0eD-A2F8woqTb@shikoro>
2026-06-09 9:26 ` [GIT PULL] rust-i2c-fixes for 7.1-rc7 Wolfram Sang
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox