From: sashiko-bot@kernel.org
To: "Philipp Stanner" <phasta@kernel.org>
Cc: dri-devel@lists.freedesktop.org, media-ci@linuxtv.org,
ojeda@kernel.org, gary@garyguo.net
Subject: Re: [RFC PATCH v6 2/5] rust: DmaFence: Implement Deref for FenceContext
Date: Fri, 16 Oct 2026 09:01:23 +0000 [thread overview]
Message-ID: <sashiko-outbox-174041@kernel.org> (raw)
In-Reply-To: <20261016085724.1031766-4-phasta@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] rust: missing #[inline] on Deref::deref in abstraction
--
commit f7dee333951179025d9c4ebf4f5a3d49e66c7f5e
Author: Philipp Stanner <phasta@kernel.org>
rust: DmaFence: Implement Deref for FenceContext
This commit implements the Deref trait for FenceContext. This allows users
to easily access the data carried by the context.
> 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]
This isn't a bug, but should this method be marked with the #[inline]
attribute?
The Rust subsystem guidelines recommend that small functions within
abstractions (such as the kernel crate) be annotated with #[inline]. Since
this deref implementation is a trivial getter returning a reference to a
struct field, omitting the attribute might lead to unnecessary function call
overhead when used frequently.
> + &self.data
> + }
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261016085724.1031766-2-phasta@kernel.org?part=2
next prev parent reply other threads:[~2026-10-16 9:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 8:57 [RFC PATCH v6 0/5] rust: Add drm::JobQueue Philipp Stanner
2026-10-16 8:57 ` [RFC PATCH v6 1/5] rust: DmaFence: remove static lifetime Philipp Stanner
2026-10-16 9:06 ` sashiko-bot
2026-10-16 8:57 ` [RFC PATCH v6 2/5] rust: DmaFence: Implement Deref for FenceContext Philipp Stanner
2026-10-16 9:01 ` sashiko-bot [this message]
2026-10-16 8:57 ` [RFC PATCH v6 3/5] rust: DmaFence: Don't drop on signal Philipp Stanner
2026-10-16 9:04 ` sashiko-bot
2026-10-16 9:49 ` Alice Ryhl
2026-10-16 8:57 ` [RFC PATCH v6 4/5] rust: DmaFence: Replace call_rcu() with synchronize_rcu() Philipp Stanner
2026-10-16 9:11 ` sashiko-bot
2026-10-16 8:57 ` [RFC PATCH v6 5/5] rust: drm: Add JobQueue Philipp Stanner
2026-10-16 9:12 ` 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=sashiko-outbox-174041@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.