From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: "Igor Korotin via B4 Relay"
<devnull+igor.korotin.linux.gmail.com@kernel.org>,
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
Subject: Re: [PATCH] MAINTAINERS: Update Rust I2C Subsystem entries
Date: Mon, 23 Mar 2026 17:34:21 +0100 [thread overview]
Message-ID: <acFrjfsk1RKsIj9A@shikoro> (raw)
In-Reply-To: <DHAB0HOXQJIV.2ZRJ1VMNEIEA6@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 313 bytes --]
On Mon, Mar 23, 2026 at 05:31:53PM +0100, 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?
Works for me
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-03-23 16:34 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 [this message]
2026-03-23 18:46 ` Igor Korotin
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=acFrjfsk1RKsIj9A@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=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 \
/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.