From: Igor Korotin <igor.korotin@linux.dev>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-i2c <linux-i2c@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
rust-for-linux@vger.kernel.org,
Danilo Krummrich <dakr@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Miguel Ojeda <ojeda@kernel.org>
Subject: [GIT PULL] rust-i2c-next for v8.0
Date: Thu, 9 Apr 2026 20:11:18 +0100 [thread overview]
Message-ID: <3f459ba1-3d03-4c44-a8f1-5ec939f9c0e5@linux.dev> (raw)
Hi Wolfram,
As discussed, here's the first pull request from rust-i2c subsystem tree
Thank you.
Igor
The following changes since commit 8fc326e15895c9f0403e6243dd4ad468b10aab3d:
Merge branch 'i2c/for-current' into i2c/for-next (2026-04-04 12:03:01
+0200)
are available in the Git repository at:
https://github.com/ikrtn/linux.git tags/rust-i2c-for-v8.0
for you to fetch changes up to b388d1f9a51d3e1ad48e1d98bfe2ca5d022e0a83:
MAINTAINERS: add Rust I2C tree and update Igor Korotin's email
(2026-04-09 19:41:00 +0100)
----------------------------------------------------------------
Add Rust I2C subsystem tree and update maintainer email
- Add Rust I2C git tree entry to MAINTAINERS for collecting patches
to be submitted upstream via the I2C tree
- Update Igor Korotin's email from igor.korotin.linux@gmail.com
to igor.korotin@linux.dev in MAINTAINERS and .mailmap
----------------------------------------------------------------
Igor Korotin (1):
MAINTAINERS: add Rust I2C tree and update Igor Korotin's email
.mailmap | 1 +
MAINTAINERS | 3 ++-
2 files changed, 3 insertions(+), 1 deletion(-)
reply other threads:[~2026-04-09 19:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3f459ba1-3d03-4c44-a8f1-5ec939f9c0e5@linux.dev \
--to=igor.korotin@linux.dev \
--cc=dakr@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox