From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Vladislav Zaharov" <vladazaharova2018@gmail.com>
Cc: <dakr@kernel.org>, <jhubbard@nvidia.com>, <aliceryhl@google.com>,
<ttabi@nvidia.com>, <gary@garyguo.net>,
<nova-gpu@lists.linux.dev>, <dri-devel@lists.freedesktop.org>,
<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v7 2/4] gpu: nova-core: gsp: move the log buffers into their own file
Date: Sat, 14 Nov 2026 11:25:30 +0900 [thread overview]
Message-ID: <DMUKT0NIC5YX.294W9XAS31304@nvidia.com> (raw)
In-Reply-To: <20261113075317.934264-3-vladazaharova2018@gmail.com>
On Fri Nov 13, 2026 at 4:53 PM JST, Vladislav Zaharov wrote:
> Move the GSP-RM log buffer code from gsp.rs into gsp/logbuffer.rs, ahead
> of extending it. No functional change.
>
> Signed-off-by: Vladislav Zaharov <vladazaharova2018@gmail.com>
> ---
> drivers/gpu/nova-core/gsp.rs | 59 +++--------------------
> drivers/gpu/nova-core/gsp/logbuffer.rs | 65 ++++++++++++++++++++++++++
> 2 files changed, 72 insertions(+), 52 deletions(-)
> create mode 100644 drivers/gpu/nova-core/gsp/logbuffer.rs
Thanks, the git `colorMoved` option makes the move obvious, and the next
patch becomes much easier to review.
Reviewed-by: Alexandre Courbot <acourbot@nvidia.com>
next prev parent reply other threads:[~2026-11-14 2:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 7:53 [PATCH v7 0/4] gpu: nova-core: retain the GSP-RM log buffers Vladislav Zaharov
2026-11-13 7:53 ` [PATCH v7 1/4] gpu: nova-core: move the debugfs root into the module data Vladislav Zaharov
2026-11-14 2:24 ` Alexandre Courbot
2026-11-13 7:53 ` [PATCH v7 2/4] gpu: nova-core: gsp: move the log buffers into their own file Vladislav Zaharov
2026-11-14 2:25 ` Alexandre Courbot [this message]
2026-11-13 7:53 ` [PATCH v7 3/4] gpu: nova-core: gsp: retain the GSP-RM log buffers after unbind Vladislav Zaharov
2026-11-13 20:34 ` Danilo Krummrich
2026-11-13 7:53 ` [PATCH v7 4/4] Documentation: nova: remove completed GSP log buffer task Vladislav Zaharov
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=DMUKT0NIC5YX.294W9XAS31304@nvidia.com \
--to=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nova-gpu@lists.linux.dev \
--cc=ttabi@nvidia.com \
--cc=vladazaharova2018@gmail.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 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.