From: Igor Korotin <igor.korotin@linux.dev>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org,
Danilo Krummrich <dakr@kernel.org>,
Miguel Ojeda <ojeda@kernel.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: [GIT PULL] rust-i2c-next for 7.3
Date: Sat, 22 Aug 2026 12:38:47 +0100 [thread overview]
Message-ID: <178739872719.9834.5401695033021882071@linux.dev> (raw)
In-Reply-To: <aodUPU8RGR1ZJlQm@zenone.zhora.eu>
Hi Andi,
No problem, rebased on i2c/i2c. Updated pull below.
Thanks
Igor
The following changes since commit 7a79b02dd1b09c235c3cf6075bccca2160d1b826:
i2c: rcar: fix reset handling for Gen5 (2026-08-19 22:07:13 +0200)
are available in the Git repository at:
https://github.com/ikrtn/linux.git tags/rust-i2c-for-7.3
for you to fetch changes up to b5fa55ad007059547c9139d4c4872e158ae255f2:
i2c: rust: mark I2cAdapter methods as inline (2026-08-22 12:22:27 +0100)
----------------------------------------------------------------
i2c: rust: mark I2cAdapter methods as inline
A single cleanup for the Rust I2C abstractions, targeting 7.3.
`I2cAdapter::get`, `inc_ref`, and `dec_ref` are trivial wrappers around
`i2c_get_adapter`/`i2c_put_adapter` and were showing up as their own
symbols in the build. Mark them `#[inline]` so they get folded into
their callers instead.
Signed-off-by: Igor Korotin <igor.korotin@linux.dev>
----------------------------------------------------------------
Nicolás Antinori (1):
i2c: rust: mark I2cAdapter methods as inline
rust/kernel/i2c.rs | 3 +++
1 file changed, 3 insertions(+)
next prev parent reply other threads:[~2026-08-22 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 21:28 [GIT PULL] rust-i2c-next for 7.3 Igor Korotin
2026-08-20 19:26 ` Andi Shyti
2026-08-22 11:38 ` Igor Korotin [this message]
2026-08-22 12:24 ` Andi Shyti
2026-08-24 7:54 ` Geert Uytterhoeven
2026-08-24 11:45 ` Andi Shyti
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=178739872719.9834.5401695033021882071@linux.dev \
--to=igor.korotin@linux.dev \
--cc=andi.shyti@kernel.org \
--cc=dakr@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