From: Igor Korotin <igor.korotin@linux.dev>
To: sfr@canb.auug.org.au
Cc: linux-next@vger.kernel.org
Subject: Please add rust-i2c-next and rust-i2c-fixes to linux-next
Date: Sat, 28 Mar 2026 21:17:32 +0000 [thread overview]
Message-ID: <02908210-0ed5-42a7-b725-8bf70f936828@linux.dev> (raw)
Hi Stephen,
Please add the following tree to linux-next:
Tree: https://github.com/ikrtn/rust-for-linux
- Branch: rust-i2c-next
- Branch: rust-i2c-fixes
This is the maintainer tree for the Rust I2C subsystem.
Thanks,
Igor
next reply other threads:[~2026-03-28 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 21:17 Igor Korotin [this message]
2026-03-28 23:59 ` Please add rust-i2c-next and rust-i2c-fixes to linux-next Stephen Rothwell
2026-03-30 11:27 ` Mark Brown
2026-03-30 13:12 ` Mark Brown
2026-04-04 14:50 ` Igor Korotin
2026-04-04 15:05 ` Mark Brown
2026-04-04 15:32 ` Igor Korotin
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=02908210-0ed5-42a7-b725-8bf70f936828@linux.dev \
--to=igor.korotin@linux.dev \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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