All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Korotin <igor.korotin@linux.dev>
To: Danilo Krummrich <dakr@kernel.org>,
	Igor Korotin via B4 Relay
	<devnull+igor.korotin.linux.gmail.com@kernel.org>
Cc: 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>,
	linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
	"Wolfram Sang" <wsa+renesas@sang-engineering.com>
Subject: Re: [PATCH] MAINTAINERS: Update Rust I2C Subsystem entries
Date: Mon, 23 Mar 2026 18:46:55 +0000	[thread overview]
Message-ID: <90810e54-3324-4100-9f04-1d4d07b20ead@linux.dev> (raw)
In-Reply-To: <DHAB0HOXQJIV.2ZRJ1VMNEIEA6@kernel.org>

On 3/23/2026 4:31 PM, Danilo Krummrich wrote:
> (Cc: Wolfram)
> 
> On Mon Mar 23, 2026 at 5:06 PM CET, Igor Korotin via B4 Relay wrote:
>> +T:	git https://github.com/ipv6forever/linux.git rust-i2c-next
> 
> I assume you plan to send the corresponding PRs to Wolfram?

Yes, I plan to send pull requests to Wolfram.

I’ll make sure to include Wolfram in the addresses next time

Thanks
Igor

  parent reply	other threads:[~2026-03-23 18:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 16:06 [PATCH] MAINTAINERS: Update Rust I2C Subsystem entries Igor Korotin
2026-03-23 16:06 ` Igor Korotin via B4 Relay
2026-03-23 16:31 ` Danilo Krummrich
2026-03-23 16:34   ` Wolfram Sang
2026-03-23 18:46   ` Igor Korotin [this message]
2026-03-23 19:03     ` Danilo Krummrich
2026-03-24 14:14       ` Miguel Ojeda
2026-03-25 22:03         ` Igor Korotin
2026-03-23 16:32 ` Gary Guo
2026-03-23 18:42   ` Igor Korotin
2026-03-26 13:40 ` Krzysztof Kozlowski

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=90810e54-3324-4100-9f04-1d4d07b20ead@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=devnull+igor.korotin.linux.gmail.com@kernel.org \
    --cc=gary@garyguo.net \
    --cc=igor.korotin.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --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.