From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Igor Korotin <igor.korotin.linux@gmail.com>
Cc: "Igor Korotin" <igor.korotin@linux.dev>,
"Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
"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>,
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: Thu, 9 Apr 2026 08:10:16 +0200 [thread overview]
Message-ID: <addCyCVBJuVHfwhs@shikoro> (raw)
In-Reply-To: <85e8de3e-cb00-4911-95b4-282bd7ec21e4@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 262 bytes --]
> 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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-04-09 6:10 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
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 [this message]
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=addCyCVBJuVHfwhs@shikoro \
--to=wsa+renesas@sang-engineering.com \
--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=igor.korotin@linux.dev \
--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 \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox