From: Andi Shyti <andi.shyti@kernel.org>
To: Igor Korotin <igor.korotin@linux.dev>
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: Thu, 20 Aug 2026 21:26:52 +0200 [thread overview]
Message-ID: <aodUPU8RGR1ZJlQm@zenone.zhora.eu> (raw)
In-Reply-To: <178717488339.2840.16053648973983973210@linux.dev>
Hi Igor,
On Wed, Aug 19, 2026 at 10:28:03PM +0100, Igor Korotin wrote:
> Hi Andi,
>
> First pull request from the rust-i2c tree for you.
Thanks for your pull request, but...
> Thank you.
>
> Igor
>
> The following changes since commit 527dd7fb6209857f8ff4426055b3a418e60faa8b:
>
> Merge branch 'i2c/i2c' into i2c/i2c-next (2026-07-29 23:40:39 +0200)
... do you mind rebasing on top of i2c/i2c rather than
i2c/i2c-next? The latter is my testing branch for both fixes and
merge window patches. While i2c/i2c is the branch where I pile up
patches for Linus.
Otherwise I would need to cherry-pick.
Sorry, I should have specified that in my kernel.org info page. I
will do it after the merge window.
Thanks,
Andi
> 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 61ddec70c9bcc3d4b0471c8683e57d3b03cecf0a:
>
> i2c: rust: mark I2cAdapter methods as inline (2026-08-09 12:04:34 +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-20 19:26 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 [this message]
2026-08-22 11:38 ` Igor Korotin
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=aodUPU8RGR1ZJlQm@zenone.zhora.eu \
--to=andi.shyti@kernel.org \
--cc=dakr@kernel.org \
--cc=igor.korotin@linux.dev \
--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