All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Korotin <igor.korotin@linux.dev>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
	"Igor Korotin" <igor.korotin.linux@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: Mon, 6 Apr 2026 14:03:56 +0100	[thread overview]
Message-ID: <c26d043d-43a8-49a9-a866-d2bd5922b549@linux.dev> (raw)
In-Reply-To: <adGOXajATeerw91I@shikoro>

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

  reply	other threads:[~2026-04-06 13:04 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 [this message]
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=c26d043d-43a8-49a9-a866-d2bd5922b549@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.