Re: [PATCH v3 1/3] rust: i2c: add basic I2C device and driver abstractions

["Danilo Krummrich" <dakr@kernel.org>]

On Sat Aug 2, 2025 at 11:07 AM CEST, Wolfram Sang wrote:
> Hi all,
>
>> > diff --git a/MAINTAINERS b/MAINTAINERS
>> > index 4f03e230f3c5..767beaa0f7c2 100644
>> > --- a/MAINTAINERS
>> > +++ b/MAINTAINERS
>> > @@ -11514,6 +11514,13 @@ F:	include/linux/i2c.h
>> >  F:	include/uapi/linux/i2c-*.h
>> >  F:	include/uapi/linux/i2c.h
>> >  
>> > +I2C SUBSYSTEM [RUST]
>> 
>> Has this been agreed with Wolfram off-list? (I'm asking since I haven't seen a
>> reply from him in v2.)
>> 
>> In case you just did not receive an answer yet, it's fine to proceed with a
>> proposal as you do here. However, please make sure to keep Wolfram in the loop.
>> :)
>
> Thank you for pointing out this thread, much appreciated. I think (I
> hope) I said previously that I am supportive of the bindings in general
> but I can't help at all because I don't speak Rust. Given that, I am
> more than happy to see this MAINTAINERS entry for Rust I2C. This part is
> definitely:
>
> Acked-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
>
>> In either case, which tree should patches flow through?
>
> As long as you don't touch generic I2C header files, I suggest some Rust
> tree. I guess patches will have more dependencies on what is in that
> tree.

Maybe it would also be a good option to take PRs from Igor? I think it could be
a great way to get in touch with some of the Rust work over time without having
to commit to maintaining it. (Of course, this is entirely up to you though.)

While I encourage the above, one fallback alternative could be to take patches
through the driver-core tree -- at least for now. Given that this is a bus
abstraction and hence most infrastructure used is generic device / driver
infrastructure, there's some synergy.

>> > +M:	Igor Korotin <igor.korotin.linux@gmail.com>
>> > +R:	Danilo Krummrich <dakr@kernel.org>
>> 
>> If you'd like me to keep an eye on this as well, this is fine with me.
>> 
>> > +L:	rust-for-linux@vger.kernel.org
>
> I think it is worth adding the Linux I2C list here as well. Other people
> there do speak Rust.

Agreed, maybe it'd also be good for you to be listed as reviewer?