From: sashiko-bot@kernel.org
To: "Alexandre Courbot" <acourbot@nvidia.com>
Cc: "Alexandre Courbot" <acourbot@nvidia.com>,
dri-devel@lists.freedesktop.org, ojeda@kernel.org,
gary@garyguo.net, "Danilo Krummrich" <dakr@kernel.org>
Subject: Re: [PATCH 10/10] gpu: nova-core: gsp: add `rpc` to RPC message send/receive methods
Date: Sun, 27 Sep 2026 11:22:24 +0000 [thread overview]
Message-ID: <20260927112225.48AC11F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260927-cmdq-rpc-v1-10-822db5af910e@nvidia.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] rust: broken rustdoc intra-doc links after method renaming
--
commit 41ab580cce9e4df6dca3c50983301c4f117e6a64
Author: Alexandre Courbot <acourbot@nvidia.com>
gpu: nova-core: gsp: add `rpc` to RPC message send/receive methods
Since we are going to introduce a second type of message, add `rpc` to
the names of the relevant command queue methods so we can distinguish
between the two.
> diff --git a/drivers/gpu/nova-core/gsp/cmdq/rpc.rs b/drivers/gpu/nova-core/gsp/cmdq/rpc.rs
> index 335f94c4d2aac..81f8c79b1bb53 100644
> --- a/drivers/gpu/nova-core/gsp/cmdq/rpc.rs
> +++ b/drivers/gpu/nova-core/gsp/cmdq/rpc.rs
[ ... ]
> @@ -216,7 +216,7 @@ fn send_command<M>(&mut self, command: M) -> Result
> }
> }
>
> - fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> {
> + fn wait_for_rpc_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> {
> let GspMessage {
[Severity: Low]
Are there stale rustdoc links in drivers/gpu/nova-core/gsp/cmdq.rs after
this rename?
drivers/gpu/nova-core/gsp/cmdq.rs:
/// This is the type returned by [`CmdqInner::wait_for_msg`].
struct GspMessage<'a> {
> header,
> contents: (slice_1, slice_2),
[ ... ]
> @@ -275,12 +275,12 @@ fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> {
> /// - `ERANGE` if the message had a recognized but non-matching function code.
> ///
> /// Error codes returned by [`MessageFromGsp::read`] are propagated as-is.
> - fn receive_msg<M: MessageFromGsp>(&mut self, timeout: Delta) -> Result<M>
> + fn receive_rpc_msg<M: MessageFromGsp>(&mut self, timeout: Delta) -> Result<M>
[Severity: Low]
Could this method rename break the intra-doc link for MessageFromGsp in
this same file?
drivers/gpu/nova-core/gsp/cmdq/rpc.rs:
/// This trait tells [`Cmdq::receive_msg`] how it can receive a given type of message.
pub(crate) trait MessageFromGsp: Sized {
> where
> // This allows all error types, including `Infallible`, to be used for `M::InitError`.
> Error: From<M::InitError>,
> {
> - let message = self.wait_for_msg(timeout)?;
> + let message = self.wait_for_rpc_msg(timeout)?;
[ ... ]
> @@ -357,22 +357,22 @@ pub(crate) fn send_command<M>(&self, command: M) -> Result<M::Reply>
> /// written to by its [`CommandToGsp::init_variable_payload`] method.
> ///
> /// Error codes returned by the command initializers are propagated as-is.
> - pub(crate) fn send_command_no_wait<M>(&self, command: M) -> Result
> + pub(crate) fn send_rpc_command_no_wait<M>(&self, command: M) -> Result
[Severity: Low]
Will this change leave a broken rustdoc link in drivers/gpu/nova-core/gsp/cmdq.rs?
drivers/gpu/nova-core/gsp/cmdq.rs:
/// Marker type representing the absence of a reply for a command. Commands using this as their
/// reply type are sent using [`Cmdq::send_command_no_wait`].
pub(crate) struct NoReply;
> where
> M: CommandToGsp<Reply = NoReply>,
> Error: From<M::InitError>,
> {
> - self.inner.lock().send_command(command)
> + self.inner.lock().send_rpc_command(command)
> }
>
> /// Receive a message from the GSP.
> ///
> /// See [`CmdqInner::receive_msg`] for details.
> - pub(crate) fn receive_msg<M: MessageFromGsp>(&self, timeout: Delta) -> Result<M>
> + pub(crate) fn receive_rpc_msg<M: MessageFromGsp>(&self, timeout: Delta) -> Result<M>
[Severity: Low]
It looks like this method rename might have missed its own doc comment right
above it:
/// See [`CmdqInner::receive_msg`] for details.
> where
> // This allows all error types, including `Infallible`, to be used for `M::InitError`.
> Error: From<M::InitError>,
> {
> - self.inner.lock().receive_msg(timeout)
> + self.inner.lock().receive_rpc_msg(timeout)
> }
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260927-cmdq-rpc-v1-0-822db5af910e@nvidia.com?part=10
next prev parent reply other threads:[~2026-09-27 11:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 11:14 [PATCH 00/10] gpu: nova-core: gsp: prepare the command queue for r000 dual-message types Alexandre Courbot
2026-09-27 11:14 ` [PATCH 01/10] gpu: nova-core: gsp: cmdq: use element_count to advance queue pointer Alexandre Courbot
2026-09-27 11:23 ` sashiko-bot
2026-09-27 11:14 ` [PATCH 02/10] gpu: nova-core: gsp: cmdq: validate checksum earlier on receive Alexandre Courbot
2026-09-27 11:23 ` sashiko-bot
2026-09-27 11:14 ` [PATCH 03/10] gpu: nova-core: gsp: introduce and use proper RpcMessageHeader type Alexandre Courbot
2026-09-27 11:25 ` sashiko-bot
2026-09-27 11:14 ` [PATCH 04/10] gpu: nova-core: gsp: cmdq: group the RPC-specific part of send_single_command Alexandre Courbot
2026-09-27 11:14 ` [PATCH 05/10] gpu: nova-core: gsp: cmdq: split the transport part of the send path Alexandre Courbot
2026-09-27 11:26 ` sashiko-bot
2026-09-27 11:14 ` [PATCH 06/10] gpu: nova-core: gsp: cmdq: move the RPC send code into a sub-module Alexandre Courbot
2026-09-27 11:14 ` [PATCH 07/10] gpu: nova-core: gsp: cmdq: split the transport part of the receive path Alexandre Courbot
2026-09-27 11:27 ` sashiko-bot
2026-09-27 11:14 ` [PATCH 08/10] gpu: nova-core: gsp: cmdq: move the RPC receive code into a sub-module Alexandre Courbot
2026-09-27 11:14 ` [PATCH 09/10] gpu: nova-core: gsp: move the RPC commands " Alexandre Courbot
2026-09-27 11:14 ` [PATCH 10/10] gpu: nova-core: gsp: add `rpc` to RPC message send/receive methods Alexandre Courbot
2026-09-27 11:22 ` sashiko-bot [this message]
2026-09-27 13:35 ` [PATCH 00/10] gpu: nova-core: gsp: prepare the command queue for r000 dual-message types Alexandre Courbot
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=20260927112225.48AC11F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=acourbot@nvidia.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=ojeda@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.