Add a git tree entry for Rust I2C development and update the
e-mail address.

The tree will be used to collect patches and provide a basis
for integration and testing, including linux-next.

Signed-off-by: Igor Korotin <igor.korotin.linux@gmail.com>
---
Changelog
---------
v2:
- Add an entry in .mailmap linking the e-mail igor.korotin@linux.dev 
with the igor.korotin.linux@gmail.com
- Improve commit message to provide more context
- Update GitHub username from ipv6forever to ikrtn, thus update git
link. 
---
 .mailmap    | 1 +
 MAINTAINERS | 3 ++-
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/.mailmap b/.mailmap
index 5ac7074c455f..3a11f89b3d5b 100644
--- a/.mailmap
+++ b/.mailmap
@@ -327,6 +327,7 @@ Henrik Rydberg <rydberg@bitmath.org>
 Herbert Xu <herbert@gondor.apana.org.au>
 Huacai Chen <chenhuacai@kernel.org> <chenhc@lemote.com>
 Huacai Chen <chenhuacai@kernel.org> <chenhuacai@loongson.cn>
+Igor Korotin <igor.korotin@linux.dev> <igor.korotin.linux@gmail.com>
 Ike Panhc <ikepanhc@gmail.com> <ike.pan@canonical.com>
 J. Bruce Fields <bfields@fieldses.org> <bfields@redhat.com>
 J. Bruce Fields <bfields@fieldses.org> <bfields@citi.umich.edu>
diff --git a/MAINTAINERS b/MAINTAINERS
index 77fdfcb55f06..f5bf555bd32c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -12021,11 +12021,12 @@ F:	include/uapi/linux/i2c-*.h
 F:	include/uapi/linux/i2c.h
 
 I2C SUBSYSTEM [RUST]
-M:	Igor Korotin <igor.korotin.linux@gmail.com>
+M:	Igor Korotin <igor.korotin@linux.dev>
 R:	Danilo Krummrich <dakr@kernel.org>
 R:	Daniel Almeida <daniel.almeida@collabora.com>
 L:	rust-for-linux@vger.kernel.org
 S:	Maintained
+T:	git https://github.com/ikrtn/linux.git rust-i2c-next
 F:	rust/kernel/i2c.rs
 F:	samples/rust/rust_driver_i2c.rs
 F:	samples/rust/rust_i2c_client.rs

---
base-commit: bf074eb6891be799174ff42e0051492681fdc045
change-id: 20260326-update-rust-i2c-maintainers-1a7f190ccc1c

Best regards,
-- 
Igor Korotin <igor.korotin@linux.dev>

On Sat, Apr 4, 2026 at 7:01 PM Igor Korotin <igor.korotin@linux.dev> wrote:
>
> Add a git tree entry for Rust I2C development and update the
> e-mail address.
>
> The tree will be used to collect patches and provide a basis
> for integration and testing, including linux-next.
>
> Signed-off-by: Igor Korotin <igor.korotin.linux@gmail.com>

I imagine this will go through Wolfram.

(The patch is sent from the new address, but the SoB is the old one --
Cc'ing the previous address.)

Cheers,
Miguel

On 4/4/2026 8:24 PM, Miguel Ojeda wrote:
> On Sat, Apr 4, 2026 at 7:01 PM Igor Korotin <igor.korotin@linux.dev> wrote:
>>
>> Add a git tree entry for Rust I2C development and update the
>> e-mail address.
>>
>> The tree will be used to collect patches and provide a basis
>> for integration and testing, including linux-next.
>>
>> Signed-off-by: Igor Korotin <igor.korotin.linux@gmail.com>
> 
> I imagine this will go through Wolfram.

Yes, Wolfram is added and aware.

> (The patch is sent from the new address, but the SoB is the old one --
> Cc'ing the previous address.)

Yeah, this is the only way to overcome the problem with b4 we talked about:
B4 catches the line in mailmap and changes the e-mail and b4 prep stops
working.

But I assume it's not that big problem. Thanks for adding previous 
e-mail to cc.

Best Regards
Igor

> > I imagine this will go through Wolfram.
> 
> Yes, Wolfram is added and aware.

Well, this doesn't apply on top of rc6, so I assume it will be included
in a i2c-rust pull request I will receive?

Hello Wolfram

On 4/4/2026 11:19 PM, Wolfram Sang wrote:
> 
>>> I imagine this will go through Wolfram.
>>
>> Yes, Wolfram is added and aware.
> 
> Well, this doesn't apply on top of rc6, so I assume it will be included
> in a i2c-rust pull request I will receive?

Yes, this will go through the i2c-rust tree and be included via the 
usual pull request.

Thanks
Igor

> Yes, this will go through the i2c-rust tree and be included via the usual
> pull request.

When will the pull request come? Merge window starts next week
probably...

Hello Wolfram

On 4/8/2026 9:16 PM, Wolfram Sang wrote:
> 
>> Yes, this will go through the i2c-rust tree and be included via the usual
>> pull request.
> 
> When will the pull request come? Merge window starts next week
> probably...
> 

Should I wait for an Ack, or is this good to go for the upcoming pull 
request?

Thanks
Igor

> Should I wait for an Ack, or is this good to go for the upcoming pull
> request?

You are the maintainer, you decide if it needs an ack ;) However, you
are modifying only your MAINTAINER entries, so it doesn't need an ack
from someone else, I'd say.