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

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

On Mon Aug 4, 2025 at 4:58 PM CEST, Igor Korotin wrote:
> On 8/2/25 01:00, Danilo Krummrich wrote:
>> On Fri Aug 1, 2025 at 5:40 PM CEST, Igor Korotin wrote:
>>> +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.
>> 
>
> Yeah. I really need your help if you don't mind. Thanks.
>
> Could you also briefly tell me finally which tree for patches should I
> use, how do I do it and if I need to represent it in the MAINTAINERS
> file somehow?

Given that Wolfram said that he prefers you to maintain the code under a
separate entry and send him PRs, you would need your own git tree where you
pick up patches, which you then send as a PR to Wolfram.

The link to the tree should go under "T:" in the MAINTAINERS file in the entry
your patch already contains.

I understand you haven't been a maintainer so far and haven't picked up patches
and send pull requests, so it can be a bit much in the beginning.

A good place to start is the "Kernel Maintainer Handbook" [1].

Additionally, if you're willing to pick up this responsibility, I'd happy to
offer you a call where we could go through the details of applying patches and
send PRs and clarify questions to ensure it's going to be a smooth experience
for everyone involved.

Once things are in place, you should clarify with Wolfram when in the release
cycle he expects you to send PRs, i.e. until which -rc before the merge window
for new patches, and if he has any additional expectations.

I know it may look a bit complicated at a first glance, but it's not as
complicated as it may appear either. :)

[1] https://docs.kernel.org/maintainer/index.html