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

[Wolfram Sang <wsa+renesas@sang-engineering.com>]

[-- Attachment #1: Type: text/plain, Size: 1558 bytes --]

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.

> > +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.

> > +S:	Maintained
> > +F:	rust/kernel/i2c.rs

Thanks,

   Wolfram

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]