From: sashiko-bot@kernel.org
To: "Philipp Stanner" <phasta@kernel.org>
Cc: dri-devel@lists.freedesktop.org, ojeda@kernel.org,
media-ci@linuxtv.org, gary@garyguo.net
Subject: Re: [RFC PATCH v4 2/3] rust: DmaFence: Implement Deref for FenceContext
Date: Tue, 29 Sep 2026 10:55:53 +0000 [thread overview]
Message-ID: <20260929105554.C37AD1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260929104703.934128-4-phasta@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] rust: dma_fence: missing #[inline] on FenceContext::deref
--
commit 4617358e176ca58ef1fbb67c98355887062d6801
Author: Philipp Stanner <phasta@kernel.org>
rust: DmaFence: Implement Deref for FenceContext
This commit implements the Deref trait for FenceContext, allowing users
to directly access the underlying data field.
> diff --git a/rust/kernel/dma_buf/dma_fence.rs b/rust/kernel/dma_buf/dma_fence.rs
> index eef2b9e93f356..0028124e6aa64 100644
> --- a/rust/kernel/dma_buf/dma_fence.rs
> +++ b/rust/kernel/dma_buf/dma_fence.rs
[ ... ]
> @@ -86,6 +86,14 @@ pub struct FenceContext<T: FenceContextOps + Send + Sync> {
> data: T,
> }
>
> +impl<T: Send + Sync + FenceContextOps> Deref for FenceContext<T> {
> + type Target = T;
> +
> + fn deref(&self) -> &Self::Target {
[Severity: Low]
Should this method be annotated with #[inline]?
According to the Rust subsystem guidelines, small functions in abstraction
crates like the kernel crate should be annotated with the #[inline] attribute
to ensure optimal inlining across crate boundaries. The newly added deref
method is a trivial one-line accessor but lacks this attribute.
> + &self.data
> + }
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260929104703.934128-2-phasta@kernel.org?part=2
next prev parent reply other threads:[~2026-09-29 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 10:47 [RFC PATCH v4 0/3] rust: Add drm::JobQueue Philipp Stanner
2026-09-29 10:47 ` [RFC PATCH v4 1/3] rust: DmaFence: remove static lifetime Philipp Stanner
2026-09-29 10:59 ` sashiko-bot
2026-09-29 10:47 ` [RFC PATCH v4 2/3] rust: DmaFence: Implement Deref for FenceContext Philipp Stanner
2026-09-29 10:55 ` sashiko-bot [this message]
2026-09-29 10:47 ` [RFC PATCH v4 3/3] rust: drm: Add JobQueue Philipp Stanner
2026-09-29 11:02 ` sashiko-bot
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=20260929105554.C37AD1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=media-ci@linuxtv.org \
--cc=ojeda@kernel.org \
--cc=phasta@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.