From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Antonin Malzieu Ridolfi" <dev@nanonej.com>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>, <nova-gpu@lists.linux.dev>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
"Daniel Almeida" <daniel.almeida@collabora.com>
Subject: Re: [PATCH] Nova: Move register definition into module using it
Date: Wed, 20 May 2026 09:59:14 +0900 [thread overview]
Message-ID: <DIN3HZV9YVU9.87C4SH46QXUH@nvidia.com> (raw)
In-Reply-To: <20260516161258.455442-1-dev@nanonej.com>
Hi Antonin, thanks for this first patch!
Note about the subject: if you look at patches under
`drivers/gpu/nova-core`, you will notice that they all use the same
prefix (`gpu: nova-core:`). Here since you touch the `gsp` module,
you'll want to refine it further to `gpu: nova-core: gsp:`.
On Sun May 17, 2026 at 1:14 AM JST, Antonin Malzieu Ridolfi wrote:
> First babystep to split the register definitions grouped in nova root
> register file to the module which actually use them.
nit: "first babystep" is irrelevant for the git history, we prefer to
keep the log strictly factual. If you want to add side-comments, you can
do so after the `---` marker - these won't be picked up when the patch
is applied.
>
> Suggested-by: Alexandre Courbot <acourbot@nvidia.com>
> Suggested-by: Danilo Krummrich <dakr@kernel.org>
> Signed-off-by: Antonin Malzieu Ridolfi <dev@nanonej.com>
> ---
> drivers/gpu/nova-core/gsp.rs | 1 +
> drivers/gpu/nova-core/gsp/cmdq.rs | 3 ++-
> drivers/gpu/nova-core/gsp/regs.rs | 11 +++++++++++
> drivers/gpu/nova-core/regs.rs | 8 --------
> 4 files changed, 14 insertions(+), 9 deletions(-)
> create mode 100644 drivers/gpu/nova-core/gsp/regs.rs
The patch in itself looks exactly like expected. The reduced visibility
is definitely nice.
I suppose you will want to send a v2 addressing this feedback; feel free
to include one or more extra obvious modules as additional patches if
you feel like it. This is the kind of rework that can be merged quickly.
prev parent reply other threads:[~2026-05-20 0:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-16 16:14 Antonin Malzieu Ridolfi
2026-05-20 0:59 ` Alexandre Courbot [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=DIN3HZV9YVU9.87C4SH46QXUH@nvidia.com \
--to=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dev@nanonej.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nova-gpu@lists.linux.dev \
--cc=simona@ffwll.ch \
/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
all inboxes | Powered by JetHome®