mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Igor Korotin <igor.korotin@linux.dev>
To: "Nicolás Antinori" <nico.antinori.7@gmail.com>
Cc: dakr@kernel.org, daniel.almeida@collabora.com, ojeda@kernel.org,
	boqun@kernel.org, gary@garyguo.net, bjorn3_gh@protonmail.com,
	lossin@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: rust: mark I2cAdapter methods as inline
Date: Sat, 23 May 2026 09:24:00 +0100	[thread overview]
Message-ID: <ed5901b7-4446-4aa3-a98c-d8696d6b47fe@linux.dev> (raw)
In-Reply-To: <20260521190937.248904-1-nico.antinori.7@gmail.com>

Hello Nicolas

On 5/21/2026 8:08 PM, Nicolás Antinori wrote:
> When building the kernel using llvm-19.1.7-rust-1.85.0-x86_64, the
> following symbols are generated:
> 
> $ nm vmlinux | grep ' _R'.*I2cAdapter | rustfilt
> ffffffff817ff380 T <kernel::i2c::I2cAdapter>::get
> ffffffff817ff400 T <kernel::i2c::I2cAdapter as kernel::sync::aref::AlwaysRefCounted>::dec_ref
> ffffffff817ff3e0 T <kernel::i2c::I2cAdapter as kernel::sync::aref::AlwaysRefCounted>::inc_ref
> 
> However, these Rust symbols are trivial wrappers around the
> `i2c_get_adapter` and `i2c_put_adapter` functions. It doesn't make sense
> to go through a trivial wrapper for these functions.
> 
> Link: https://github.com/Rust-for-Linux/linux/issues/1145
> Suggested-by: Alice Ryhl <aliceryhl@google.com>
> Signed-off-by: Nicolás Antinori <nico.antinori.7@gmail.com>
> ---
>   rust/kernel/i2c.rs | 3 +++
>   1 file changed, 3 insertions(+)
> 
> diff --git a/rust/kernel/i2c.rs b/rust/kernel/i2c.rs
> index 7b908f0c5a58..07f9fd53c4e5 100644
> --- a/rust/kernel/i2c.rs
> +++ b/rust/kernel/i2c.rs
> @@ -397,6 +397,7 @@ pub fn index(&self) -> i32 {
>       }
>   
>       /// Gets pointer to an `i2c_adapter` by index.
> +    #[inline]
>       pub fn get(index: i32) -> Result<ARef<Self>> {
>           // SAFETY: `index` must refer to a valid I2C adapter; the kernel
>           // guarantees that `i2c_get_adapter(index)` returns either a valid
> @@ -416,11 +417,13 @@ pub fn get(index: i32) -> Result<ARef<Self>> {
>   
>   // SAFETY: Instances of `I2cAdapter` are always reference-counted.
>   unsafe impl AlwaysRefCounted for I2cAdapter {
> +    #[inline]
>       fn inc_ref(&self) {
>           // SAFETY: The existence of a shared reference guarantees that the refcount is non-zero.
>           unsafe { bindings::i2c_get_adapter(self.index()) };
>       }
>   
> +    #[inline]
>       unsafe fn dec_ref(obj: NonNull<Self>) {
>           // SAFETY: The safety requirements guarantee that the refcount is non-zero.
>           unsafe { bindings::i2c_put_adapter(obj.as_ref().as_raw()) }

Reviewed-by: Igor Korotin <igor.korotin@linux.dev>

I'll take it through Rust I2C next

Thanks
Igor

      parent reply	other threads:[~2026-05-23  8:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21 19:08 Nicolás Antinori
2026-05-22  5:09 ` Onur Özkan
2026-05-23  8:24 ` Igor Korotin [this message]

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=ed5901b7-4446-4aa3-a98c-d8696d6b47fe@linux.dev \
    --to=igor.korotin@linux.dev \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=nico.antinori.7@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome