From: Igor Korotin <igor.korotin@linux.dev>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Igor Korotin <igor.korotin.linux@gmail.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v2] MAINTAINERS: add Rust I2C tree and update Igor Korotin's email
Date: Sat, 4 Apr 2026 22:22:40 +0100 [thread overview]
Message-ID: <707e9f2e-048a-469e-adbb-17334dd027ab@linux.dev> (raw)
In-Reply-To: <CANiq72nzNa29_YduauW_qwPq9sLbYa+28ykq42_bbfLnOqUm9Q@mail.gmail.com>
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
next prev parent reply other threads:[~2026-04-04 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 17:01 [PATCH v2] MAINTAINERS: add Rust I2C tree and update Igor Korotin's email Igor Korotin
2026-04-04 19:24 ` Miguel Ojeda
2026-04-04 21:22 ` Igor Korotin [this message]
2026-04-04 22:19 ` Wolfram Sang
2026-04-06 13:03 ` Igor Korotin
2026-04-08 20:16 ` Wolfram Sang
2026-04-08 20:31 ` Igor Korotin
2026-04-09 6:10 ` Wolfram Sang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=707e9f2e-048a-469e-adbb-17334dd027ab@linux.dev \
--to=igor.korotin@linux.dev \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=igor.korotin.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=wsa+renesas@sang-engineering.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.